maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gordon Cody <>
Subject Re: AW: AW: AW: mvn release:prepare does not update parent version
Date Sat, 09 Nov 2013 13:31:21 GMT
You may want to upgrade maven itself once more. It is not just maven itself
but the combination of plugins that are used and your environment matters.
Ensure that each maven goal you plan on using in your environment actually
works in your environment before you need it for real. Maven has to work
with your vcs, your artifact mgmt (nexus/artifactory/other), your network
security policies, etc. all at the same time.

When we began upgrading existing projects from mvn-2.0.9 we had to also
upgrade numerous plugins. It took some effort to find the combination of
plugins/configuration that allowed us to do 'mvn deploy' successfully with
mvn-3.0.4. But 'mvn release' did not work in our environment until
mvn-3.0.5 was released!!. Underlying plugin(s) had changed.

Regards, Gord

On Sat, Nov 9, 2013 at 4:55 AM, Markus Karg <> wrote:

> Robert,
> no need to teach me about completeness of reports -- I am in the reverse
> situation day by day as you can imagine. The problem was that I had the
> problem since I migrated to Maven 3 from day one with even the smallest
> possible POM (it looked 'obvious' to me) and did not have the idea there
> might be a fix already already which is not contained in Maven 3 so far. In
> fact this is why I would love to have the ability to use version ranges in
> plugin dependencies! ;-)
> Anyways, as all is fixed now, thanks for the kind help! :-)
> -Markus
> -----Original Message-----
> From: Robert Scholte []
> Sent: Freitag, 8. November 2013 18:52
> To: Maven Users List
> Subject: Re: AW: AW: AW: mvn release:prepare does not update parent version
> Op Fri, 08 Nov 2013 16:30:30 +0100 schreef Markus Karg <>:
> > I wonder why someone fixed it but didn't close
> >!
> Well, is was probably already fixed for a long time. Since you only had a
> description it will take some time to fix it, since it must first be
> reproducible. That's why attaching a sample project helps, and a patch with
> a possible fix even more.
> In this case it was the log-file which triggered me: first update the
> version of the plugin and see if it has been already been fixed.
> It is all about being as complete as possible :)
> Robert
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Best Regards, Gord Cody

Release Manager  Zafin Labs Americas Inc.
179 Colonnade Road-Suite 100, Ottawa ON, Canada
Phone: +1 (613) 216-2504  Fax: +1 (613) 688-1374  Mobile: +1 613-601-2734
Web:  Email:

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