Maven 2 is great and stable for the basic things.
If you wanna do exotic things you might have to resort to the antrun
plugin (for purposes like the maven 1 maven.xml).
The eclipse plugin in maven 2 work well to generate configuration.
The idea plugin in maven 2 works well if you use the snapshot instead of
the latest release.
The maven 2 plugin in Eclipse seems broken.
The maven 2 plugin in NetBeans looks very nice.
So unless you're using NetBeans, get comfortable with opening your
command shell to generate a new IDE configuration every time you add a
new library.
If you want to generate a multiproject site, also use the snapshot of
the site plugin.
Ray Ward wrote:
I read Vincent Massol's PPT dated 15 September 2005. He said, Short answer:
No.
But, that was 5 months ago! How about now?
I have a major set of J2EE apps that are mostly all in m1, with a few
stragglers in Ant. I will be going through these, externalizing the
environmental dependencies from inside the app to properties files of some
kind. So it is tempting to upgrade from m1 to m2 in the process.
What are the risks? Suicidal? None? Olympic downhill skiiers only?
Curlers would be comfortable? ;-)
TIA,
Ray Ward, PMP
--
With kind regards,
Geoffrey De Smet
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
