I think the maven 2 release is mature enough in its core. The plugins
need to catch-up. Again overall great job Maven team!

Also is there a road map to what are the priorities the maven team is
addressing and general project progress.

Sanjay Shukla,
HPI Product Engineering, 2 Penn Plaza, NY.
212 904 3629 Office
732 692 4419 Cell
 

-----Original Message-----
From: jerome lacoste [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 15, 2006 10:42 AM
To: Maven Users List
Subject: Re: m2 -- Ready for Prime Time, yet?

On 2/14/06, Ray Ward <[EMAIL PROTECTED]> 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?  ;-)

To my point of view, the main risks are the bugs you might encounter
and might delay your migration.

The builds are more stable though and the issues mostly exhibited when
you start doing things people haven't done before (new plugins, ...).
As Brett said it, you might need to use SNAPSHOTS versions of some
plugins.

Second writing a m2 plugin takes longer than writing an ant plugin. Be
sure to grasp the various concepts (lifecycle, repositories ...). Get
your dev infrastructure ready early.

If you are not too time constrained, go for it. The earlier you start,
the better you will be to report potential issues and get them fixed
before the next stable release. Make sure you try to tackle the
unsupported bits early.

Cheers,

Jerome

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

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

Reply via email to