Hi Jim,

> -----Original Message-----
> From: Jim Mochel [mailto:[EMAIL PROTECTED]
> Sent: mercredi 8 juin 2005 17:34
> To: Maven Users List
> Cc: 'Maven Users List'
> Subject: Re: [Mavenbook.org] What content would you like to see?
> 
> I believe this is for documenting Maven 1.x , correct ?
> 
> If so, I would suggest some sort of documentation about the different
> scopes and namespaces of ANT Properties, Maven Properties. the POM
> attributes,  and the Jelly variables. A lot of trial and error and walking
> through 100s of mailing list emails went into discovering what worked in
> getting a POM variable into a property or a Jelly variable anbd determing
> which are visible to whom.
> 
> I consider the
> http://wiki.astrogrid.org/bin/view/Astrogrid/UsefulMavenNotes note to have
> saved me HOURs of walking through plugin source to make things happen so
> most of those tricks

Yes, I believe this is what we are doing with our "Tips" news.
 
> I would actually hope that you would forsake documenting 1.x for maven
> 2.0. My reasons really boil down to Maven 1.x feels like a proof of
> concept and Maven 2 has already (in its Alpha version) eliminated almost
> all of the workarounds I had to implement to  make 1.x work on my
> projects. Please take that has kudo's for 2.0 rather than slamming 1.0

Sure but Maven 2.0 is far from being ready to be used on a production
project while Maven 1.x is and is being used by thousands of people. They do
not have the same maturity.

But to reassure you the goal is not to be Maven 1.x centric. It just happens
that Tim and I have 4 years of experience of using Maven 1.x and thus our
tips come from that experience. As we progress in our learning of Maven 2.x,
we'll add tips about Maven 2 too.

I encourage you to help us out and add you m2 tips too! The more the funnier
:-)

[snip]

Thanks for the feedback
-Vincent


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to