We only have this:
http://maven.apache.org/guides/development/guide-m2-
development.html#Creating%20and%20submitting%20a%20patch
Which I will update and I was going to stick a big fat message on the
issue creation screen.
On 5 Jun 07, at 6:17 PM 5 Jun 07, John Casey wrote:
Do we have this caveat on our website anywhere?
Just curious.
-john
On Jun 5, 2007, at 4:50 PM, Jason van Zyl wrote:
Hi,
If you are reporting issues please don't waste your time and ours
by not providing a way for us to reproduce your problem.
Descriptions of the problems take an inordinate amount of time to
process as we have to make a usable POM to even attempt to assess
the problem. Issues stating problems without something usable to
try (let alone test cases, or integration tests) will be closed as
incomplete. If you're going to take the time to cut out snippets
of your POM please attach a working POM, or a set of POMs, that we
can download and run. We appreciate reports, and patches better
but if you don't have something usable for us it's incredibly hard
to us to manage the issues. A POM goes a long way to helping us
resolve problems.
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---
John Casey
Committer and PMC Member, Apache Maven
mail: jdcasey at commonjava dot org
blog: http://www.ejlife.net/blogs/john
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
