r
> > emailing
> > this list.
> >
> > This list spends more time writing and wading through the repeating
> > large
> > email volume than updating docs for all to use and reduce the need for
> > email
> > list questions.
> >
> >
> >
ough the repeating
> > large
> > email volume than updating docs for all to use and reduce the need for
> > email
> > list questions.
> >
> >
> > -Original Message-
> > From: Ramin Farhanian [mailto:[EMAIL PROTECTED]
> > Sent: Friday, Janu
updating docs for all to use and reduce the need for
> email
> list questions.
>
>
> -Original Message-
> From: Ramin Farhanian [mailto:[EMAIL PROTECTED]
> Sent: Friday, January 20, 2006 12:31 AM
> To: Maven Users List
> Subject: Re: Worst documentation in the wh
pdating docs for all to use and reduce the need for email
list questions.
-Original Message-
From: Ramin Farhanian [mailto:[EMAIL PROTECTED]
Sent: Friday, January 20, 2006 12:31 AM
To: Maven Users List
Subject: Re: Worst documentation in the whole apache projects
Afkham,
We might contrib
Just want to say that I do not agree.
Isn't your rant just because you couldn't get a J2EE multiproject
working? A multiproject guide with ears/wars is indeed becoming really
crucial.
There are plenty of other mini-guides and a good pom/settings
references. Overall better then when maven 1 c
hi,
I do suggest a wiki page to document the "BEST PRACTICE" for maven 2.
I agree an idea that a good tool does not need much documentation;
btw, anyone needs a manual for iPod ?
so, I hope m2 should be as seamless and intuitive as possible. (yes,
M2 is heading the right direction. that w
Afkham,
We might contribute some examples to Maven team but
It's better that we do not expose it ourselves.
Because Most of maven users might have understood a
version of truth about Maven mechanism. I really like
the team to give Maven aware people a homework
example. This way they dont start sam
Hi Folks,
I sincerely wish that everybody commenting on the bad documetation
will at least try to contribute some documentation. After all, most of
you have figured out stuff the hard way. Why not share it with the
community? Why keep on blaming the developers for insufficient
documentation, and no
The nature of an open souce project is not an excuse
not to document. We are facing 50 different MVC
frameworks. What if they don't have documentation?
Open source projects are there to let all of us live
in a more harmonized, more peaceful, ever evolving
world. You code here today in Maven, I w
grow and thrive
Phill
-Original Message-
From: Miguel Griffa [mailto:[EMAIL PROTECTED]
Sent: January 19, 2006 10:21 AM
To: Maven Users List
Subject: Re: Worst documentation in the whole apache projects
very well said!
I thinnk this kind ot mail would be totally ok in a commercial and
ommitters and the
> user-base, have been very supportive regardless if there was
> documentation related to the issue. :-)
>
> Keep Maven rolling!
>
> -D
>
>
>> -Original Message-
>> From: Peschier J. (Jeroen) [mailto:[EMAIL PROTECTED]
&
been very supportive regardless if there was
documentation related to the issue. :-)
Keep Maven rolling!
-D
> -Original Message-
> From: Peschier J. (Jeroen) [mailto:[EMAIL PROTECTED]
> Sent: Thursday, January 19, 2006 11:15 AM
> To: Maven Users List
> Subject: RE: Wors
n get with open source projects... Let's hope the same
thing doesn't happen to Maven.
-Oorspronkelijk bericht-
Van: Miguel Griffa [mailto:[EMAIL PROTECTED]
Verzonden: donderdag 19 januari 2006 16:21
Aan: Maven Users List
Onderwerp: Re: Worst documentation in the whole apache pr
I've have to totally agree. 200% The documentation is a total joke, it's hard
to read and the
maintainers don't seem to care to create a consolidated reference.
And, the book by Vincent Massol and Tim O'Brien is just a total rag. I mean
really, full of typos
and everything. C'mon, if Maven
documented open source tools :-)
just my two cents...
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf
> Of Carlos
> Sanchez
> Sent: Mittwoch, 18. Januar 2006 22:01
> To: Maven Users List
> Subject: Re: Worst documentation in the whole apache
very well said!
I thinnk this kind ot mail would be totally ok in a commercial and expensive
support forum of a build system,
but definetly not an open source one.
I also think documentation is a strong - in maven, but that's why I've tried
to help on it a little, contributing is the way,
On 1/18
Yes, that's one of the reasons why I'm switching from Maven 1 to Maven 2.
It's just better. (But although it's released, it's not really done...)
-K
On 1/19/06 7:31 AM, "Richard Allen" <[EMAIL PROTECTED]> wrote:
> I'm amazed at the lack of appreciation some people have for getting
> something f
> -Original Message-
> From: Jeff Jensen [mailto:[EMAIL PROTECTED]
>
> But sometimes the patches sit and rot...
> http://jira.codehaus.org/browse/MNG-1479
Maybe what we need as users is to set up (or start using) a wiki.
It seems like there are two maven2 wikis: one at apache.org and o
rs List
Subject: RE: Worst documentation in the whole apache projects
Yes. Go here http://jira.codehaus.org/browse/MNG and look through the
components that start with "documentation". Pick something that interests
you, write the docs for it and attach your documentation to the issue.
W
I'm amazed at the lack of appreciation some people have for getting
something for nothing! Maven is FREE! The developers don't get paid to
write the code, much less the documentation, or even to respond to lousy
user email. They do it all in their free time. However, I bet Roberto is
getting pa
You can also use maven 1 and you'll find a lot of documentation in the web.
There's also :
- a book written by Vincent Massol & Tim O'Brien *Maven*: A *Developer's
Notebook*
- an article :http://www.onjava.com/pub/a/onjava/2005/09/07/maven.html
A book for maven 2 will be available in some we
You can choose:
- using it with the documentation it has
- create your own system and document it to the extent you want
just good luck if you choose second option ;)
On 1/18/06, Nanamura, Roberto <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Is there any way to improve all the documentation for the Maven
I have similar issues, but I still think it's useful enough to go ahead. But
then, I'm not doing J2EE, just Hibernate/Tomcat apps.
-K
On 1/18/06 1:52 PM, "Nanamura, Roberto" <[EMAIL PROTECTED]>
wrote:
> Hi,
>
> Is there any way to improve all the documentation for the Maven.
>
> I will not us
Yes. Go here http://jira.codehaus.org/browse/MNG and look through the
components that start with "documentation". Pick something that
interests you, write the docs for it and attach your documentation to
the issue. We'll get it into the next version.
An open source project is only as good as it
24 matches
Mail list logo
