Re: Maven book: feedback

2006-07-18 Thread Henning P. Schmiedehausen
Sebastien Arbogast [EMAIL PROTECTED] writes: OTOH there's already open documentation on the Maven wiki and in Maven's svn. It's not because it's open that people contribute more or that the quality is better... IMHO, Wiki is too open, SVN is not open enough. A CMS would be a

Re: Maven book: feedback

2006-07-17 Thread Michael . Wiles
Have been following this thread with interest. One of my biggest issues with maven 2 is that the documentation is very poor. Yes, I know there is a book on it, but I did not find the book very helpful... The maven book takes a far too high level approach and does not give detailed

Re: Maven book: feedback

2006-07-17 Thread Jeff Mutonho
Vincent , I guess the lack of flow is what I perhaps was trying to illustrate in our chat the other day.To a total newbie , things get pretty confusing as to how to put it all together in order to have a working build environment.I wouldn't be a good thing for people to be scared away from M2

RE: Maven book: feedback

2006-07-17 Thread Matilda Robert
Users List Subject: Re: Maven book: feedback Have been following this thread with interest. One of my biggest issues with maven 2 is that the documentation is very poor. Yes, I know there is a book on it, but I did not find the book very helpful... The maven book takes a far too high level

Re: Maven book: feedback

2006-07-17 Thread Brett Porter
so that they know that the user guide is just that a guide and not the only source for information. Matilda -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, July 17, 2006 8:29 AM To: Maven Users List Subject: Re: Maven book: feedback Have been following

RE: Maven book: feedback

2006-07-16 Thread Vincent Massol
Hi Sebastien, I'm glad that you liked the m1 book ;-) but I'm sorry that you don't like the new m2 one... There are probably several reasons. One of them may be that it's hard to write with a consistent voice and consistent progression when several authors write at the same time. OTOH this has

Re: Maven book: feedback

2006-07-16 Thread Sebastien Arbogast
Why not trying to innovate then? Why not getting the source code of the book available to the community and make its improvement a community effort? It could be an interesting experiment: using the current version as a working basis, you could allow people to pinpoint parts that could be

RE: Maven book: feedback

2006-07-16 Thread Vincent Massol
- From: Sebastien Arbogast [mailto:[EMAIL PROTECTED] Sent: dimanche 16 juillet 2006 21:39 To: Maven Users List Subject: Re: Maven book: feedback Why not trying to innovate then? Why not getting the source code of the book available to the community and make its improvement a community effort

Re: Maven book: feedback

2006-07-16 Thread Sebastien Arbogast
Subject: Re: Maven book: feedback Why not trying to innovate then? Why not getting the source code of the book available to the community and make its improvement a community effort? It could be an interesting experiment: using the current version as a working basis, you could allow people