maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Hoffer <dhoff...@gmail.com>
Subject Re: Maven 3.2.3 upgrade
Date Tue, 09 Dec 2014 00:44:02 GMT
One other issue came up in this upgrade.  We still have branches that have
to stay at 3.0.x.  How can I make the trunk build use 3.2.3 w/o changing
everyone's M2_HOME?  Is there a way to bootstrap the build so the build
picks the specified version of Maven?  E.g. I want the build to specify the
version used not the system.

-Dave

On Mon, Dec 8, 2014 at 2:41 PM, Hervé BOUTEMY <herve.boutemy@free.fr> wrote:

> Le lundi 8 décembre 2014 13:01:10 David Hoffer a écrit :
> > I'm contemplating an upgrade of a large Maven 3.0.4 build to 3.2.3, just
> > wondering if anyone knows of either any key gotchas in the upgrade and/or
> > key benefits?
> you should check compatibility issues known with some plugins:
> https://cwiki.apache.org/confluence/display/MAVEN/AetherClassNotFound
>
> some are fixed if you're using recent version of the affected plugins,
> some are
> not yet fixed
>
>
> for the benefits, choose your favorite from release notes
> http://maven.apache.org/release-notes-all.html
>
> >
> > One feature I'm wondering at the outset is...with 3.2.3 can I specify the
> > reporting plugin versions in pluginManagement or does this still need to
> be
> > done manually?
> see https://jira.codehaus.org/browse/MNG-5477
> so changing Maven version is just about avoiding a misleading warning
> What is important is maven-site-plugin version.
>
> And see https://jira.codehaus.org/browse/MSITE-516
> maven-site-plugin version 3.4 has major improvement regarding
> pluginManagement
>
> Regards,
>
> Hervé
>
> >
> > -Dave
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message