Hi Nicolas, > -----Original Message----- > From: Nicolas Chalumeau [mailto:[EMAIL PROTECTED] > Sent: mardi 7 juin 2005 21:38 > To: Maven Users List > Subject: Re: [Mavenbook.org] What content would you like to see?
[snip] > A really good thing but there's must be a good categorisation of the > tips. ie common error, plugin dev tips. That will come when we have lots of them. ATM we have published 4 tips only and are adding one every week (roughly). > But i don't think that specific > plugin tips should be here. The better tips is where to find the good > information source I do agree that plugin tips should find their way in the plugin documentation in the end. That said, it can be a 2 step process: - tips can be given about using a special feature of a plugin - the information can then be fed in the plugin's documentation Also, I think that a plugin's tip is good as it'll serve as evangelizing a specific feature of a plugin that might not have been found otherwise (there are few people that spend all their time reading all the reference documentation). So highlighting a special plugin feature is a good thing. For example, I've just posted tip#4 about adding the download menu on the generated web site (http://mavenbook.xwiki.com/xwiki/bin/view/Main/Tip4DownloadMenu). I think it's a useful tip even though it's a plugin tip. > I have the same point of view as you. More the official maven site IS > the good place for annoucement. A web page that list the last > version/annoucement of the plugin could be a good thing in the maven > site for people that are not on the mailling list. I have proposed a solution in an email to the maven dev list yesterday (title: " RE: latest plugin releases on the maven download page "). Here it is: " I think we should do the following: - Have a CI for the Maven plugins web site so that it is published every few hours - If the site build fails, an email is sent to the maven dev mailing list with the error - Make sure the multichanges plugin gets built as part of the plugins site (I've checked and it is actually still there in the report list, so it's just a matter or running the site build) - Improve the multichanges plugin to add a RSS feed. - Advertise it This will allow people to get a fresh list of the latest version of plugins. This will allow them to get RSS notifications as soon as a new plugin is released (and I'll stop what I've started on mavenbook.org, i.e. announcing plugin releases). WDYT? " [snip] > A big propaganda page and feed back from compagny/user Things like : > - how to make my development director choose to use maven. > - What maven change in my every day job? > - How to make my developer use maven when they say that there's IDE > compile there java code and they don't need more? > - Why maven make that I code better ? > > I have some responce of this question that i have used but having some > other point of view could be a good and interresting thing to read. Sounds more like a wiki you're asking here, no? I guess this could be an interesting thing to do on the Maven wiki. The Mavenbook.org web site is more oriented towards news. For all content and resources, I believe the main maven web site (or associated wiki) is a better place. > If you have write this book like the JUnit one I now this kind of > information can be found in this one but having them online could be a > good thing for the communauty Some of it is there yes, but not that much. It's more a hands-on book (how to do things rather than why to do them). This is the format of the O'Reilly Developer Notebook series. Thanks -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
