RE: AW: AW: AW: mvn release:prepare does not update parent version
> Date: Sat, 9 Nov 2013 08:31:21 -0500
> Subject: Re: AW: AW: AW: mvn release:prepare does not update parent version
> From: gordon.c...@zafin.com
> To: users@maven.apache.org
>
> 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,
MG>dev .. svn but in prod.. git was used
your artifact mgmt (nexus/artifactory/other),
MG>ours was nexus but I can see configuration deltas biting the release manager
your network security policies,
MG>we could download point releases
MG>mega updates from http sites located outside the firewall were and are a
no-no
MG>and could get you in hot water real quick in a 'secure' environment (such as
a bank)
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!!
MG>Another big delta
MG>What are the implications for this delta to your dependency object graph?
MG>for child s What are the implications for this delta to your object
graph?
. Underlying plugin(s) had changed.
MG>Exactly..What are the implications for your plugins object graph?
MG>look at this dependency from maven-release-plugin
org.apache.maven.release
maven-release-manager
${project.version}
MG>notice maven-release-plugin and maven-release-manager are inextricably
linked on same version
MG>the release-manager plugin prompts the user for version specific questions
MG>maven-release-plugin is the plugin that does the work from the questions
asked by release-manager
MG>follow up question: why the separation?
> Regards, Gord
MG>Well put Gordon!!!
>
> 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 [mailto:rfscho...@apache.org]
> > 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
> > > https://jira.codehaus.org/browse/MRELEASE-837...!
> >
> > 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: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
>
>
> --
> 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: http://zafin.com Email: gordon.c...@zafin.com
Re: AW: AW: AW: mvn release:prepare does not update parent version
I'm pretty sure that by far most projects are released with 2.0, since
this has been the default for Apache Maven for many releases. IIRC this
has been updated for Maven 3.0.3, so if you don't specify the version, 2.0
will be used.
Now let's review this thread:
1. Markus describes his issue
2. Maximiliano asks the most important question (2 thumbs up!)
3. However, Markus answers this with 2.4.2, but in the end this was a
wrong assumption. It was actually 2.0.
Only with the evidence attached to MRELEASE-837 it was easy for me help.
Mark, don't feel bad, because this is by far the most common mistake for
the maven-release-plugin: assuming you're using the latest and greatest (
Maven2 used to pick that one up, right? ) but still relying on a very old
version.
There were enough issues which could be closed by just updating the
version.
@MG I'm a bit lost by your comments
1. Which docs are you talking about?
2. What are you trying to do here? If this is about trying to figure out
where it was actually fixed, Markus should try to release his project with
the versions between 2.0 and 2.4.2, where my guess is 2.4 due to a
complete rewrite of this code as part of MRELEASE-511.
Anyhow, I'm not going to apply a specific patch to older releases.
3. See previous bullet.
What do you mean with the fireworks? The only issues I've seen with the
2.4.x releases were GIT related or credentials related. A reference to a
JIRA issue would help.
Robert
[1] https://jira.codehaus.org/browse/MRELEASE-511
Op Sat, 09 Nov 2013 14:17:57 +0100 schreef Martin Gainty
:
From: k...@quipsy.de
To: users@maven.apache.org
Date: Fri, 8 Nov 2013 16:30:30 +0100
Subject: AW: AW: AW: mvn release:prepare does not update parent version
Martin,
thank you for your explanations, but as it turned out the problem is
fixed simply by using version 2.4.2 of the release plugin. I wonder why
someone fixed it but didn't close
https://jira.codehaus.org/browse/MRELEASE-837...!
MG>maven-release-plugin is one of most frequently used plugins used from
maven
MG>there are at least 1000+ installations out there still using the
2.1.x maven-release-plugin
MG>1000 installations out there still using 2.2.x maven-release-plugin
MG>slightly less than 1000 installations out there using 2.3.x
maven-release-management
MG>many of these installations are "secure" and disallow "autoUpdate"
from http URLs for plugins
MG>Why? ...change ${maven.plugin.version} to 2.4.2 and watch the
fireworks!
MG>the justification for breaking thru firewall instead of using own
nexus repository is tenuous
MG>but ..secure sites will allow 'point patches'
MG>3 items need to be completed:
MG>1)fix the doc to say in 2.4.2 "parent version will be updated from
development-version"
MG>This will get the legalities of "What we Say" and "What we Do" in
sync...
MG>2)backport the 2.4.2 patch to previous 2.1.x, 2.2.x, 2.3.x point
patches specifically:
MG>2a) backport 2.4.2 fix to patch 2.1.x and run testcases
MG>2b) backport 2.4.2 fix to patch 2.2.x and run testcases
MG>2c) backport 2.4.2 fix to patch 2.3.x and run testcases
MG>3)once the patch is in place and accepted by all ...close 837!
MG>Process violation was the culprit here ..(Agile Project Champions and
Stakeholders have been alerted!)
Thanks for all
-Markus
MG>you are welcome
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: AW: AW: AW: mvn release:prepare does not update parent version
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 [mailto:rfscho...@apache.org] > 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 > > https://jira.codehaus.org/browse/MRELEASE-837...! > > 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: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- 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: http://zafin.com Email: gordon.c...@zafin.com
RE: AW: AW: AW: mvn release:prepare does not update parent version
> From: k...@quipsy.de
> To: users@maven.apache.org
> Date: Fri, 8 Nov 2013 16:30:30 +0100
> Subject: AW: AW: AW: mvn release:prepare does not update parent version
>
> Martin,
>
> thank you for your explanations, but as it turned out the problem is fixed
> simply by using version 2.4.2 of the release plugin. I wonder why someone
> fixed it but didn't close
https://jira.codehaus.org/browse/MRELEASE-837...!
MG>maven-release-plugin is one of most frequently used plugins used from maven
MG>there are at least 1000+ installations out there still using the 2.1.x
maven-release-plugin
MG>1000 installations out there still using 2.2.x maven-release-plugin
MG>slightly less than 1000 installations out there using 2.3.x
maven-release-management
MG>many of these installations are "secure" and disallow "autoUpdate" from http
URLs for plugins
MG>Why? ...change ${maven.plugin.version} to 2.4.2 and watch the fireworks!
MG>the justification for breaking thru firewall instead of using own nexus
repository is tenuous
MG>but ..secure sites will allow 'point patches'
MG>3 items need to be completed:
MG>1)fix the doc to say in 2.4.2 "parent version will be updated from
development-version"
MG>This will get the legalities of "What we Say" and "What we Do" in sync...
MG>2)backport the 2.4.2 patch to previous 2.1.x, 2.2.x, 2.3.x point patches
specifically:
MG>2a) backport 2.4.2 fix to patch 2.1.x and run testcases
MG>2b) backport 2.4.2 fix to patch 2.2.x and run testcases
MG>2c) backport 2.4.2 fix to patch 2.3.x and run testcases
MG>3)once the patch is in place and accepted by all ...close 837!
MG>Process violation was the culprit here ..(Agile Project Champions and
Stakeholders have been alerted!)
>
> Thanks for all
> -Markus
MG>you are welcome
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
RE: AW: AW: AW: mvn release:prepare does not update parent version
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 [mailto:rfscho...@apache.org] 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 > https://jira.codehaus.org/browse/MRELEASE-837...! 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: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
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 https://jira.codehaus.org/browse/MRELEASE-837...! 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: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: AW: AW: mvn release:prepare does not update parent version
Martin, thank you for your explanations, but as it turned out the problem is fixed simply by using version 2.4.2 of the release plugin. I wonder why someone fixed it but didn't close https://jira.codehaus.org/browse/MRELEASE-837...! Thanks for all -Markus - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
