Peter Horlock wrote:
>
> Hey, Tim,
>
> where are you??? One year ago, you wrote and wrote and wrote for "The
> definitive guide".
> Now it's in Version 0.6 and not much if not nothing at all has changed
> during the last months.
> Also, I can't wait to see the new Maven cookbook! Maybe you got an alpha
> at
> hand?
> Just let me know, I would be at hand to read it and to give you some
> feedback!
>
> I've got my copy of the Definitive guide, and I would buy the cookbook
> right
> away -
> if I could. Seems like you'r doing too much of sonatype / nexus / maven
> training / m2eclipse, hmmm?
> ;-)
>
> Don't let them stop you from writing - keep up the good work!
>
> Peter
>
>
Well thanks for the note, I'm still around. The priority for a while has
been this book: http://tr.im/rnFW
The community has established Maven as the solid choice it might not have
been in 2006 by focusing on quality and keeping up the pace of releases.
I'm sensing that "we" (and when I say "we", I mean the community of users
and developers), have to fight less to achieve Maven adoption at a company
or on a project now that Maven is a solid and tested tool. I'm not
convinced that a majority of our audience is convinced about repository
management, and that's one of the reasons why I felt that we needed a
separate book on repository management. I also didn't want the Maven book
to become a 1000-page book (see the sendmail book).
Look for the repo book to get a little thicker over the next month, and then
expect the m2eclipse book (which was also once a chapter in the maven def
guide) to get some attention after that. We do need a Maven Cookbook, I
don't have a secret alpha, but there is a GitHub repo for the effort that
has been seeded with the Nexus book content.
--
View this message in context:
http://www.nabble.com/Cookbook-tp24385718p24391200.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]