This is an interesting thread one that strikes at the heart of open source in the marketplace. A product paid for or not needs to be complete, functional and correct. To stop short is just that. The documentation like QA testing is required to consider the job complete. I am a long time coder and much prefer the excitement of coding than the effort of documenting. I am also a new adopter to Maven and cannot move over until this is closer to a complete product. Core developers should complete documentation like test cases during checking, the same goes for plug-ins. A main concern around raised later in this thread about major open source project that fail/die (e.g. XDoclet). It is hard to justify ones expense of time to install, learn and configure a product if it is likely to fade away.
All that being said I add this email in the hopes that this excellent product will continue to 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 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/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote: > > 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 will not use Maven anymore since there are a bunch of thing > > missing from the documentation (and a lot of things do not work like > > the J2EE archetype which is nowhere to be find and I am not the only > > one to complain about it). > > > > It is good for a simple project (then again, why should I need maven > > for a simple Hello World project?). But if you add a J2EE layer or > > other components, it simpy does not have document (for example no > > document for the topic: "Guide to creating a multi-module build"). > > Then how should I create a multi-project maven? What is this > > artifactId and groupID? What the hell it keeps on going to the > > repo1.maven.org repository for my sub-projects? What are the examples? No samples? > > > > The reference is a joke. How can a reference be so laconious? It is > > a reference so every tag in the XML must have a good description > > (even the description in the generated xml is better than the reference!). > > > > I do not recommend Maven to anyone starting a serious project for > > lack of documentation and erroneous documentation. > > > > I spent the whole day try to make it work for a simple J2EE project, > > then I had to google it several times for each error (it should be > > in the document web-site). > > Whereas I would take one hour to create the directories, my build > > and deployment ant targets. > > > > Thanks but I'd rather do not use it, > > > > Roberto > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Miguel Griffa Skype: miguel.griffa Y!: m_griffa MSN: [EMAIL PROTECTED] Cell: 54-911-62519355 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
