You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by "Asmann, Roland" <Ro...@adesso.at> on 2010/12/12 18:48:15 UTC
Differences between Maven 2.0, 2.1, 2.2 and 3.0
Hi all,
Could someone tell me what the differences between 2.0, 2.1, 2.2 and 3.0
are? I am currently running on 2.0.9 and 2.0.10 (depending on the
project) and I was wondering if I should start migrating.
Currently I am not allowed to upgrade to 3.0 (a 2.x version is still
mandatory), but maybe I could at least make a suggestion to switch to
3.0 -- depending on how big the migration would turn out to be.
Thanks.
--
Roland Asmann
Senior Software Engineer
adesso Austria GmbH
Floridotower 26. Stock T +43 1 2198790-27
Floridsdorfer Hauptstr. 1 F +43 1 2198790-927
A-1210 Wien M +43 664 88657566
E roland.asmann@adesso.at
W www.adesso.at
-------------------------------------------------------------
>>> business. people. technology. <<<
-------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Differences between Maven 2.0, 2.1, 2.2 and 3.0
Posted by Anders Hammar <an...@hammar.net>.
Well, most of it no (as it is a free-style job). The publication you can
control what phase you execute ("mvn deploy").
There is work for Maven 3 integration in Hudson going on though.
However, this Hudson discussion is more suitable on the Hudson list.
/Anders
On Mon, Dec 13, 2010 at 11:51, Paul Merlin <es...@n0pe.org> wrote:
> Quoting Anders Hammar <an...@hammar.net>:
> > Hudson does support Maven 3 through free-style jobs.
>
> Sure, but do you get nice maven integration in hudson like the list of
> modules,
> repositories per job, artifact publication out of maven execution and so on
> ?
>
> Not that you can recreate that manually but it's painfull.
>
> /Paul
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Differences between Maven 2.0, 2.1, 2.2 and 3.0
Posted by Paul Merlin <es...@n0pe.org>.
Quoting Anders Hammar <an...@hammar.net>:
> Hudson does support Maven 3 through free-style jobs.
Sure, but do you get nice maven integration in hudson like the list of modules,
repositories per job, artifact publication out of maven execution and so on ?
Not that you can recreate that manually but it's painfull.
/Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Differences between Maven 2.0, 2.1, 2.2 and 3.0
Posted by Anders Hammar <an...@hammar.net>.
Hudson does support Maven 3 through free-style jobs.
/Anders
On Mon, Dec 13, 2010 at 10:19, Zac Thompson <za...@gmail.com> wrote:
> On Sun, Dec 12, 2010 at 9:48 AM, Asmann, Roland <Ro...@adesso.at>
> wrote:
> > Hi all,
> >
> > Could someone tell me what the differences between 2.0, 2.1, 2.2 and 3.0
> > are? I am currently running on 2.0.9 and 2.0.10 (depending on the
> > project) and I was wondering if I should start migrating.
> >
> > Currently I am not allowed to upgrade to 3.0 (a 2.x version is still
> > mandatory), but maybe I could at least make a suggestion to switch to
> > 3.0 -- depending on how big the migration would turn out to be.
>
> http://maven.apache.org/release-notes-2.x.html
>
> To sum up:
> 2.1 is broken
> 2.2 requires Java 1.5 and adds default execution IDs for plugins
> 3.0 is the new hotness: works just like 2.2 but better.
>
> If you're already on Java 1.5 or later, then switching to 3.x may
> actually be the easiest upgrade option because of the "better" part.
> Your biggest work will probably be getting approval to update plugins
> to v3-compatible versions. Once you've done that (or while doing it),
> I recommend that you attempt building all of your existing projects
> with 3.0.1 and fix any errors or warnings; I'm pretty confident you
> can safely do that while still doing official builds with 2.0.x.
> Maven 3 warnings are usually about things you probably should fix
> anyway.
>
> I've been slowly migrating projects away from v2 for release builds,
> but using v3 for all my working builds for some time now, without any
> negative consequence so far. An earlier reply mentioned Hudson, I
> think to point out that Hudson does not yet support Maven 3 and that
> is a meaningful obstacle for some people. I'm using maven 2.2.1 for
> CI builds with Hudson for that reason. In my experience 3.0 is
> *highly* backwards compatible from the user's perspective.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Differences between Maven 2.0, 2.1, 2.2 and 3.0
Posted by Zac Thompson <za...@gmail.com>.
On Sun, Dec 12, 2010 at 9:48 AM, Asmann, Roland <Ro...@adesso.at> wrote:
> Hi all,
>
> Could someone tell me what the differences between 2.0, 2.1, 2.2 and 3.0
> are? I am currently running on 2.0.9 and 2.0.10 (depending on the
> project) and I was wondering if I should start migrating.
>
> Currently I am not allowed to upgrade to 3.0 (a 2.x version is still
> mandatory), but maybe I could at least make a suggestion to switch to
> 3.0 -- depending on how big the migration would turn out to be.
http://maven.apache.org/release-notes-2.x.html
To sum up:
2.1 is broken
2.2 requires Java 1.5 and adds default execution IDs for plugins
3.0 is the new hotness: works just like 2.2 but better.
If you're already on Java 1.5 or later, then switching to 3.x may
actually be the easiest upgrade option because of the "better" part.
Your biggest work will probably be getting approval to update plugins
to v3-compatible versions. Once you've done that (or while doing it),
I recommend that you attempt building all of your existing projects
with 3.0.1 and fix any errors or warnings; I'm pretty confident you
can safely do that while still doing official builds with 2.0.x.
Maven 3 warnings are usually about things you probably should fix
anyway.
I've been slowly migrating projects away from v2 for release builds,
but using v3 for all my working builds for some time now, without any
negative consequence so far. An earlier reply mentioned Hudson, I
think to point out that Hudson does not yet support Maven 3 and that
is a meaningful obstacle for some people. I'm using maven 2.2.1 for
CI builds with Hudson for that reason. In my experience 3.0 is
*highly* backwards compatible from the user's perspective.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Differences between Maven 2.0, 2.1, 2.2 and 3.0
Posted by Jesse Farinacci <ji...@gmail.com>.
Hi Roland,
On Sun, Dec 12, 2010 at 12:48 PM, Asmann, Roland
<Ro...@adesso.at> wrote:
>
> Could someone tell me what the differences between 2.0, 2.1, 2.2 and 3.0
> are? I am currently running on 2.0.9 and 2.0.10 (depending on the
> project) and I was wondering if I should start migrating.
Any attempt to describe the differences is going to be a failure. You
should read the comprehensive changelog found here:
http://jira.codehaus.org/browse/MNG#selectedTab=com.atlassian.jira.plugin.system.project%3Achangelog-panel
You should definitely start migrating. It's only a matter of time
before the plugins stop being Maven 2.0.x compatible, and I'm already
seeing lots of requirements for 2.2.x and even 3.0.x!!
> Currently I am not allowed to upgrade to 3.0 (a 2.x version is still
> mandatory), but maybe I could at least make a suggestion to switch to
> 3.0 -- depending on how big the migration would turn out to be.
Maven 3 is exceptionally well tested for backwards compatibility, I
consider it a mistake to spend resources and time updating from 2.0.x
to 2.2.x when it's already been displaced by 3.0.x.
-Jesse
--
There are 10 types of people in this world, those
that can read binary and those that can not.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Differences between Maven 2.0, 2.1, 2.2 and 3.0
Posted by Benson Margulies <bi...@gmail.com>.
Hudson?
On Sun, Dec 12, 2010 at 5:34 PM, Stephen Connolly
<st...@gmail.com> wrote:
> 2.1 is a dead duck do not use it. There are major issues with it
>
> 2.2 requires java 1.5 to run and is the end of the 2.x code base (i.e. the
> one where the first version of a plugin loaded in a multi module build is
> the only version loaded)
>
> 3.0 is the way to go
>
> - Stephen
>
> ---
> Sent from my Android phone, so random spelling mistakes, random nonsense
> words and other nonsense are a direct result of using swype to type on the
> screen
> On 12 Dec 2010 17:48, "Asmann, Roland" <Ro...@adesso.at> wrote:
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Differences between Maven 2.0, 2.1, 2.2 and 3.0
Posted by Stephen Connolly <st...@gmail.com>.
2.1 is a dead duck do not use it. There are major issues with it
2.2 requires java 1.5 to run and is the end of the 2.x code base (i.e. the
one where the first version of a plugin loaded in a multi module build is
the only version loaded)
3.0 is the way to go
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 12 Dec 2010 17:48, "Asmann, Roland" <Ro...@adesso.at> wrote: