I'd like to take a stab at creating a more user-oriented version of
http://maven.apache.org/guides/development/guide-m2-development.html.
The current page is not something that users are like to stumble upon
considering where it's at and its current contents. The new page will be
aimed at users who has stumbled upon something that is not working, and
the steps that they should be taking to get it resolved:
"Maven is not working - what should I do"
Here's an outline of what should be in there, in no particular order:
- Searching the user-list archives
- Asking on the user list
- Submitting an issue (where, how, what to include etc.)
- Creating a pom that can be used to verify that it is a bug
- Creating a patch that fixes the problem
And also stuff, which I don't have necessary skill to write about, which
Jason touched upon in another mail:
- Creating test cases
- Creating integration tests
Since this is a new page I'll start on a new one in svn, unless someone
feels strongly against that. The other alternative being the wiki.
Brett Porter wrote:
(moved to dev@)
Jason,
Is there any way we can get this text into the issue submission form
itself? I think people need the just in time reminder.
- Brett
On 06/06/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
