[ http://jira.codehaus.org/browse/MNG-1521?page=comments#action_50697 ]
Peter Pilgrim commented on MNG-1521: ------------------------------------ I second this emotion. I am struggling with Maven multi-module and getting to javadoc plugin to generate group packaging documentation. In fact I gave up yesterday, because there were no answers. The source code should be made more accessible with src.zip file, if possible. Maybe maven2-core-src.zip, and then maven2-core-plugins-src.zip and then maven2-core-advanced-plugins-src.zip is the way to go. Peter > Maximize the use of the Apache wiki page for Maven > -------------------------------------------------- > > Key: MNG-1521 > URL: http://jira.codehaus.org/browse/MNG-1521 > Project: Maven 2 > Type: Task > Components: documentation - general > Reporter: Anuerin Diaz > > > From the Maven user list (Alexander Hars) > ================ > Hi, > I have been using Maven2 for two weeks and am very impressed by all the > great features. > However, the learning curve is steep and it is often very difficult to > find certain answers (I often need to > to look at the source code to find them). Whenever I find an answer to a > question, I alone have learned. > Others don't profit. I would be quite willing to submit an answer to > Maven2 for inclusion into the guides. But that takes > quite a bit of time (...going into CVS, downloading the apt file, > modifying it, testing it, submitting it to someone for posting > to the CVS etc.). I did that once, but we can't expect big progress in > the documentation to occur this way. > The only solution that does not overload the developers (who put in so > much time already anyhow), is to make better use > of the wiki because everybody can contribute and increase our cumulated > knowledge. But just providing the wiki as > it is now (http://wiki.apache.org/maven/Maven2Info) does not work. There > is almost nothing there, almost nobody > goes to it, therefore few people add anything either. > There are two practical ways in which we could make better use of the wiki: > a) provide a prominent link from the Maven2 documentation (guides, > miniguides, references, etc.) to a related wiki > page. Anyone who has some insight to add to the documentation can place > it there; anyone who has not found the > answer in the standard documentation can easily check whether there is > more information in the wiki. From time > to time someone can integrate the bulk of good insights from the wiki > back into the documentation. > b) put most of the documentation into the wiki. In my opinion this is > the ideal case, because it would reduce the > load on the developers for providing the documentation and there would > be a single documentation mechanism. > But it is probably not practical because the Maven Wiki is not based on > the .apt format and integration with the > maven site generation mechanism may be difficult. > Option a) is very easy to do. We would only need to create associated > wiki pages and insert a link to the wiki > page from the original documentation. I am sure that we could greatly > expand the Maven-related knowledge > this way. > I certainly would be willing to work on the necessary changes to get > this rolling if you think this is a good idea. > ================================ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
