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]
