well i would agree in principle but the maven2 plugin matrix you list is hopelessly out of date, and always has been.
my current irritation is that i have no idea what the latest versions of most plugins are and what their compatability status with maven 2.0.2 is. I foolishly upgraded to 2.0.2 and now can't get my projects to build properly anymore.
Kind regards,
Dave Sag
Bengt-Erik Fröberg <[EMAIL PROTECTED]> wrote on 19-01-2006 17:19:20:
> I have posted a wish in JIRA on some kind of standard for plugin
> documentation à la http://cargo.codehaus.org/Maven2+plugin. Under
> "Documentation". Vote for it if you agree!
>
> Regards,
>
> /B-E
>
>
> -----Ursprungligt meddelande-----
> Från: Tim OBrien [mailto:[EMAIL PROTECTED]
> Skickat: den 19 januari 2006 17:05
> Till: Maven Users List
> Ämne: Re: Worst documentation in the whole apache projects
>
> 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 were so EASY, why wold we need to read
> anything to know how to
> use it.
>
> How do they expect us to start a multi-project build when the help
> documentation is TOTALLY BLANK!
> And, the fact that Maven forces you to use the ibiblio
> repository....puh-lease.
>
> You are right though, really I'd have to recommend gmake from now on. Maven
> is for the birds. I
> mean, seriously, what are we paying these people for!?!
>
> :-)
>
> Tim O'Brien
> [EMAIL PROTECTED]
>
>
>
> --- "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]
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
