[jira] (MRELEASE-297) release doesn't bump versions in properties to the next dev iteration
[ https://jira.codehaus.org/browse/MRELEASE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-297. --- Resolution: Fixed Fix Version/s: 2.2.2 Assignee: Benjamin Bentmann (was: Maria Odea Ching) Seems to be fixed by Benjamin with [rev. 1083092|http://svn.apache.org/viewvc?view=revision&revision=1083092], which is indeed version 2.2.2 It's a huge diff, so it's quite hard to pinpoint the exact lines. > release doesn't bump versions in properties to the next dev iteration > - > > Key: MRELEASE-297 > URL: https://jira.codehaus.org/browse/MRELEASE-297 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: prepare >Affects Versions: 2.0-beta-6, 2.0-beta-7 >Reporter: Brian Fox >Assignee: Benjamin Bentmann > Fix For: 2.2.2 > > > Properties used as versions are correctly updated to the release version and > committed, but they are not bumped to the next snapshot after. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-297) release doesn't bump versions in properties to the next dev iteration
[
https://jira.codehaus.org/browse/MRELEASE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=288514#comment-288514
]
Marc von Renteln edited comment on MRELEASE-297 at 1/17/12 2:55 AM:
Yes, I can confirm this for 2.2.2 (with Maven 2.2.1). The POM gets updated
correctly. ( The issue was still present in 2.1.)
The following output at the end of release:prepare is also new:
[INFO] Transforming 'dataaccess'...
[INFO] Updating ${dataaccess.version} to 1.9-SNAPSHOT
[INFO] Ignoring artifact version update for expression ${dataaccess.version}
because it is already updated
[INFO] Ignoring artifact version update for expression ${dataaccess.version}
because it is already updated
[INFO] Ignoring artifact version update for expression ${dataaccess.version}
because it is already updated
[INFO] Ignoring artifact version update for expression ${dataaccess.version}
because it is already updated
[INFO] Ignoring artifact version update for expression ${dataaccess.version}
because it is already updated
[INFO] Ignoring artifact version update for expression ${dataaccess.version}
because it is already updated
[INFO] Ignoring artifact version update for expression ${dataaccess.version}
because it is already updated
Great to see this fixed.
was (Author: mvonrenteln):
Yes, I can confirm this for 2.2.2. The POM gets updated correctly. ( The
issue was still present in 2.1.)
The following output at the end of release:prepare is also new:
[INFO] Transforming 'dataaccess'...
[INFO] Updating ${dataaccess.version} to 1.9-SNAPSHOT
[INFO] Ignoring artifact version update for expression ${dataaccess.version}
because it is already updated
[INFO] Ignoring artifact version update for expression ${dataaccess.version}
because it is already updated
[INFO] Ignoring artifact version update for expression ${dataaccess.version}
because it is already updated
[INFO] Ignoring artifact version update for expression ${dataaccess.version}
because it is already updated
[INFO] Ignoring artifact version update for expression ${dataaccess.version}
because it is already updated
[INFO] Ignoring artifact version update for expression ${dataaccess.version}
because it is already updated
[INFO] Ignoring artifact version update for expression ${dataaccess.version}
because it is already updated
Great to see this fixed.
> release doesn't bump versions in properties to the next dev iteration
> -
>
> Key: MRELEASE-297
> URL: https://jira.codehaus.org/browse/MRELEASE-297
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.0-beta-6, 2.0-beta-7
>Reporter: Brian Fox
>Assignee: Maria Odea Ching
>
> Properties used as versions are correctly updated to the release version and
> committed, but they are not bumped to the next snapshot after.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-297) release doesn't bump versions in properties to the next dev iteration
[ https://jira.codehaus.org/browse/MRELEASE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=288515#comment-288515 ] Martin Todorov commented on MRELEASE-297: - Great! :) One suggestion: perhaps those particular info messages should be converted to debug ones? > release doesn't bump versions in properties to the next dev iteration > - > > Key: MRELEASE-297 > URL: https://jira.codehaus.org/browse/MRELEASE-297 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: prepare >Affects Versions: 2.0-beta-6, 2.0-beta-7 >Reporter: Brian Fox >Assignee: Maria Odea Ching > > Properties used as versions are correctly updated to the release version and > committed, but they are not bumped to the next snapshot after. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-297) release doesn't bump versions in properties to the next dev iteration
[
https://jira.codehaus.org/browse/MRELEASE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=288514#comment-288514
]
Marc von Renteln edited comment on MRELEASE-297 at 1/17/12 2:55 AM:
Yes, I can confirm this for 2.2.2 (with Maven 2.2.1). The POM gets updated
correctly. ( The issue was still present in 2.1.)
The following output at the end of release:prepare is also new:
[INFO] Transforming 'dataaccess'...
[INFO] Updating ${dataaccess.version} to 1.9-SNAPSHOT
[INFO] Ignoring artifact version update for expression ${dataaccess.version}
because it is already updated
[INFO] Ignoring artifact version update for expression ${dataaccess.version}
because it is already updated
Great to see this fixed.
was (Author: mvonrenteln):
Yes, I can confirm this for 2.2.2 (with Maven 2.2.1). The POM gets updated
correctly. ( The issue was still present in 2.1.)
The following output at the end of release:prepare is also new:
[INFO] Transforming 'dataaccess'...
[INFO] Updating ${dataaccess.version} to 1.9-SNAPSHOT
[INFO] Ignoring artifact version update for expression ${dataaccess.version}
because it is already updated
[INFO] Ignoring artifact version update for expression ${dataaccess.version}
because it is already updated
[INFO] Ignoring artifact version update for expression ${dataaccess.version}
because it is already updated
[INFO] Ignoring artifact version update for expression ${dataaccess.version}
because it is already updated
[INFO] Ignoring artifact version update for expression ${dataaccess.version}
because it is already updated
[INFO] Ignoring artifact version update for expression ${dataaccess.version}
because it is already updated
[INFO] Ignoring artifact version update for expression ${dataaccess.version}
because it is already updated
Great to see this fixed.
> release doesn't bump versions in properties to the next dev iteration
> -
>
> Key: MRELEASE-297
> URL: https://jira.codehaus.org/browse/MRELEASE-297
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.0-beta-6, 2.0-beta-7
>Reporter: Brian Fox
>Assignee: Maria Odea Ching
>
> Properties used as versions are correctly updated to the release version and
> committed, but they are not bumped to the next snapshot after.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-297) release doesn't bump versions in properties to the next dev iteration
[
https://jira.codehaus.org/browse/MRELEASE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=288514#comment-288514
]
Marc von Renteln commented on MRELEASE-297:
---
Yes, I can confirm this for 2.2.2. The POM gets updated correctly. ( The issue
was still present in 2.1.)
The following output at the end of release:prepare is also new:
[INFO] Transforming 'dataaccess'...
[INFO] Updating ${dataaccess.version} to 1.9-SNAPSHOT
[INFO] Ignoring artifact version update for expression ${dataaccess.version}
because it is already updated
[INFO] Ignoring artifact version update for expression ${dataaccess.version}
because it is already updated
[INFO] Ignoring artifact version update for expression ${dataaccess.version}
because it is already updated
[INFO] Ignoring artifact version update for expression ${dataaccess.version}
because it is already updated
[INFO] Ignoring artifact version update for expression ${dataaccess.version}
because it is already updated
[INFO] Ignoring artifact version update for expression ${dataaccess.version}
because it is already updated
[INFO] Ignoring artifact version update for expression ${dataaccess.version}
because it is already updated
Great to see this fixed.
> release doesn't bump versions in properties to the next dev iteration
> -
>
> Key: MRELEASE-297
> URL: https://jira.codehaus.org/browse/MRELEASE-297
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.0-beta-6, 2.0-beta-7
>Reporter: Brian Fox
>Assignee: Maria Odea Ching
>
> Properties used as versions are correctly updated to the release version and
> committed, but they are not bumped to the next snapshot after.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-297) release doesn't bump versions in properties to the next dev iteration
[ https://jira.codehaus.org/browse/MRELEASE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=288385#comment-288385 ] Christian Schulte edited comment on MRELEASE-297 at 1/16/12 5:19 AM: - This seems to have been fixed as of version '2.2.2'. Can someone confirm ? was (Author: schulte2005): This seems to haven been fixed as of version '2.2.2' of the 'maven-release-plugin'. Can someone confirm ? > release doesn't bump versions in properties to the next dev iteration > - > > Key: MRELEASE-297 > URL: https://jira.codehaus.org/browse/MRELEASE-297 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: prepare >Affects Versions: 2.0-beta-6, 2.0-beta-7 >Reporter: Brian Fox >Assignee: Maria Odea Ching > > Properties used as versions are correctly updated to the release version and > committed, but they are not bumped to the next snapshot after. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-297) release doesn't bump versions in properties to the next dev iteration
[ https://jira.codehaus.org/browse/MRELEASE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=288385#comment-288385 ] Christian Schulte commented on MRELEASE-297: This seems to haven been fixed as of version '2.2.2' of the 'maven-release-plugin'. Can someone confirm ? > release doesn't bump versions in properties to the next dev iteration > - > > Key: MRELEASE-297 > URL: https://jira.codehaus.org/browse/MRELEASE-297 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: prepare >Affects Versions: 2.0-beta-6, 2.0-beta-7 >Reporter: Brian Fox >Assignee: Maria Odea Ching > > Properties used as versions are correctly updated to the release version and > committed, but they are not bumped to the next snapshot after. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
