There is a group of people currently working on a Maven 2 book that promises to be the preferred reference. I think Carlos, Vincent, and Brett are working on that tome.
But, in terms of contributed to the online documentation. I'd suggest the following because this project could use the help. There are various levels at which you can help: Easiest: Just identify gaps in the online documentation. Sign up for a JIRA account here: http://jira.codehaus.org/secure/Dashboard.jspa, and file as many documentation bugs or wishes as you would like. More Involved: Checkout maven or the plugin you wish to document and submit patches to JIRA. I'd suggest joining the dev mailing list, but no invitation is required to participate. Tim O'Brien [EMAIL PROTECTED] --- "Hines, John" <[EMAIL PROTECTED]> wrote: > I do some writing at work. Is there already a team doing maven 2 > documentation? How do I get in contact with them? > > John Hines > [EMAIL PROTECTED] > > -----Original Message----- > From: Kathryn Huxtable [mailto:[EMAIL PROTECTED] > Sent: Thursday, January 19, 2006 8:50 AM > To: Maven Users List > Subject: Re: Worst documentation in the whole apache projects > > 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 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 paid to work on his J2EE project. Maven hasn't been > > > around as long as many other Apache open-source projects. Open-source > > projects typically have poor documentation while the code is maturing. > > > Like all open-source projects, if you want to really get to know the > > product, then read the code! It'll make you a better programmer. If > > you don't have time to read the code, then you shouldn't be using > > open-source projects. At least not until the project has matured. > > > > I'm working on a build for a complex web application and I've found > > that Maven solves problems that Ant doesn't have a solution for. In > > particular, Maven handles transitive dependencies and is multiproject > > aware. If you are using Ant alone, then you have to write your own > > solution for these things. For things that Ant has but Maven is > > currently lacking, you can write your own plugin(s) or use the > > maven-antrun-plugin. > > > > Richard Allen > > > > > > Nanamura, Roberto 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] > > > > -- > Kathryn Huxtable > Middleware Architect > Core Middleware > Information Technology, a division of Information Services The > University of Kansas > > > --------------------------------------------------------------------- > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
