I think that after this bunch of releases we'll reach a good state of stability.
I found pretty useful to comment on the jira issues with patches
asking for unit tests and docs, saying that without them it'd take lot
longer to get the patch applied (or it wouldn't be applied at all).
People usual
I've already got a start at a more comprehensive set of documentation for
the assembly plugin on localhost. I'll try to flesh it out today and get it
committed...it shouldn't take more than a day to document a plugin, even one
as complex as the assembly plugin.
-john
On 5/8/06, Brett Porter <[EM
Mike Perham wrote:
Brett, I appreciate the concern on the subject.
My main concern is not thorough documentation - it's basic "what is this
and what is it for" doucmentation. Adding goals to a plugin but not
including basic user documentation just perpetrates Maven's reputation
as a poorly docu
Mike Perham wrote:
Brett, I appreciate the concern on the subject.
My main concern is not thorough documentation - it's basic "what is this
and what is it for" doucmentation. Adding goals to a plugin but not
including basic user documentation just perpetrates Maven's reputation
as a poorly docu
ing SVN edge but once they are released
I can start contributing to the documentation myself.
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Monday, May 08, 2006 6:43 PM
To: Maven Developers List
Subject: re: plugin docs was: [vote] Release maven-assembly-plugin 2.1
Lukas Theussl wrote:
In principle I think that 3) should be enforced. Always. Releasing
components in an undocumented state means releasing them in an
unfinished state, which is shortsighted and irresponsible. It is unfair
towards users who don't regularly read the mailing list.
I totally ag
[snip]
We should never have gotten into this situation, but I think the best
balance is:
1) do as much doc as is practically possible before the release
2) release as is to satisfy users demanding the fixes/features and to
reduce load on the users list (many faqs are addressed by things like
Mike Perham wrote:
-1 due to missing documentation.
John, I built the site but I don't see any documentation on the new
features and how to use them. Did I just miss something?
No, they weren't updated by those contributing patches. This mostly
occurred before we had our previous discussio
