How I wish you could have kathy Sierra aside you in documentation. Most of the Maven documentation sounds like a reference. They are scattered and only 20% of developers can find what they need. Although I find it a brilliant tool and I can never go back to Ant, I do say that I wish there was a non-developer guy out there to document Maven. What amazes me is that there's no good example of maven 1 or 2. Nothing can be like a good example. Different versions of Maven Idea by different teams without a good documentation and declaring restrictions is so hard and has made me quite nervous. So This is what I do, I read the plugin itself. Honestly how many people can do that? If you could have two samples in the getting started, life could be so easier for everyone trying to approach Maven. The first sample could be easy and the second one complicated. Thanks for reading my complaints, Ramin ps, I find your tools briliant, don't get me wrong. I am tired of these documents. Bengt-Erik Fröberg <[EMAIL PROTECTED]> wrote: I use Maven 2, and I agree on the state of the docs, although I realize this is the deal with open-source software, for better or for worse.
I've looked into Ivy framework to see if docs were more complete and transparent, but at the time I was so exhausted by looking for answers, reading webpages and docs on M2 with poor layout etc. so I decided to go along with M2. Personally, I don't go along trying to do multiple module builds and stuff, it's just to unclear and buggy unless you want to spend 80% of development time trying to figure out exactly what is wrong. No, I let Maven 2 handle the dependencies which it does well (hrmm, at least when the reflexive dependencies exist in repository or some hot-shot developer uses a red-hot-smoking-fresh version for dependency). The trick as I see it is not to go to the next version of your dependencies at once, just wait and let the bugs and errors be resolved. Use Maven 2 along with the antrun plugin, do your build stuff in ANT, and use M2 together with a good IDE like Eclipse. Then it's really helpful. I've looked into maven 1, and I'm amazed anyone had the stamina to learn and then use it. Thank God (in that perspective) for M2. Regards, /B-E -----Ursprungligt meddelande----- Från: Arnaud HERITIER [mailto:[EMAIL PROTECTED] Skickat: den 18 januari 2006 22:22 Till: Maven Users List Ämne: Re: Worst documentation in the whole apache projects 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 weeks / months !! Arnaud On 1/18/06, Carlos Sanchez 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 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
