Considering Maven is the work of volunteers I understand it comes with no kind of warranty as to the quality of the product or the documentation. However, since Maven is portrayed as an Apache project you certain expectations are raised.
High profile open source projects like Maven should act responsibly instead of hiding behind the "no warranty" claim. Payroll developers using Maven for production work expect something to work. Some of the features Maven claim to have are, at best, unfinished. I have been evaluating Maven since 2.0 but we have not yet switched because features are lacking or not-quite-there-yet. Development on Maven seems active so I am optimistic about it maturing to a level to be used in production environments. I am quite the dualist on this. Open source projects are great when there's an active community supporting the project. We have seen good things die out last year like XDoclet... XDoclet has not seen a new release since may 2005. There are many bugs that need fixing in XDoclet. Contributions of non-committers are not even integrated or even checked anymore. The maintainers no longer seem to care. Just an example of how bad things can get with open source projects... Let's hope the same thing doesn't happen to Maven. -----Oorspronkelijk bericht----- Van: Miguel Griffa [mailto:[EMAIL PROTECTED] Verzonden: donderdag 19 januari 2006 16:21 Aan: Maven Users List Onderwerp: 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]
