You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brian Fox (JIRA)" <ji...@codehaus.org> on 2007/11/19 14:30:40 UTC
[jira] Created: (MRELEASE-297) release doesn't bump versions in
properties to the next dev iteration
release doesn't bump versions in properties to the next dev iteration
---------------------------------------------------------------------
Key: MRELEASE-297
URL: http://jira.codehaus.org/browse/MRELEASE-297
Project: Maven 2.x Release Plugin
Issue Type: Bug
Affects Versions: 2.0-beta-7, 2.0-beta-6
Reporter: Brian Fox
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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-297) release doesn't bump versions in
properties to the next dev iteration
Posted by "Hans Beemsterboer (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=215282#action_215282 ]
Hans Beemsterboer commented on MRELEASE-297:
--------------------------------------------
I had the same problem without using version properties.
It looks like the development versions get bumped up when you change method updateDomVersion as follows:
{code:title=AbstractRewritePomsPhase.java|borderStyle=solid}
if ( dependency != null )
{
versionElement = dependency.getChild( "version", dependencyRoot.getNamespace() );
if ( versionElement != null )
{
dependencyVersion = versionElement.getTextTrim();
if (mappedVersion != null && mappedVersion.endsWith("SNAPSHOT") )
{
rewriteValue( versionElement, mappedVersion );
}
}
}
{code}
> release doesn't bump versions in properties to the next dev iteration
> ---------------------------------------------------------------------
>
> Key: MRELEASE-297
> URL: http://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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-297) release doesn't bump versions in
properties to the next dev iteration
Posted by "Jan Arend Jansen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158964#action_158964 ]
Jan Arend Jansen commented on MRELEASE-297:
-------------------------------------------
Before
{code:xml}
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>nl.test</groupId>
<artifactId>release-test</artifactId>
<packaging>pom</packaging>
<name>Test Releases</name>
<version>0.0.2-SNAPSHOT</version>
<modules>
<module>release-module1</module>
</modules>
<properties>
<module1.version>0.0.2-SNAPSHOT</module1.version>
</properties>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.0-beta-8</version>
</plugin>
</plugins>
</build>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>nl.test</groupId>
<artifactId>release-module1</artifactId>
<version>${module1.version}</version>
</dependency>
</dependencies>
</dependencyManagement>
<scm>
<connection>scm:svn:https://****/svn/repos/tests/trunk/</connection>
</scm>
</project>
{code:xml}
After:
{code:xml}
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>nl.test</groupId>
<artifactId>release-test</artifactId>
<packaging>pom</packaging>
<name>Test Releases</name>
<version>0.0.3-SNAPSHOT</version>
<modules>
<module>release-module1</module>
</modules>
<properties>
<module1.version>0.0.2</module1.version>
</properties>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.0-beta-8</version>
</plugin>
</plugins>
</build>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>nl.test</groupId>
<artifactId>release-module1</artifactId>
<version>${module1.version}</version>
</dependency>
</dependencies>
</dependencyManagement>
<scm>
<connection>scm:svn:https://****/svn/repos/tests/trunk/</connection>
</scm>
</project>
{code:xml}
> release doesn't bump versions in properties to the next dev iteration
> ---------------------------------------------------------------------
>
> Key: MRELEASE-297
> URL: http://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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
Posted by "Marc von Renteln (JIRA)" <ji...@codehaus.org>.
[ 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
Posted by "Marc von Renteln (JIRA)" <ji...@codehaus.org>.
[ 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] Updated: (MRELEASE-297) release doesn't bump versions in
properties to the next dev iteration
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MRELEASE-297:
-------------------------------------
Component/s: prepare
> release doesn't bump versions in properties to the next dev iteration
> ---------------------------------------------------------------------
>
> Key: MRELEASE-297
> URL: http://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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MRELEASE-297) release doesn't bump
versions in properties to the next dev iteration
Posted by "Jan Arend Jansen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158964#action_158964 ]
Jan Arend Jansen edited comment on MRELEASE-297 at 12/22/08 9:17 AM:
---------------------------------------------------------------------
Before
{code:xml}
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>nl.test</groupId>
<artifactId>release-test</artifactId>
<packaging>pom</packaging>
<name>Test Releases</name>
<version>0.0.2-SNAPSHOT</version>
<modules>
<module>release-module1</module>
</modules>
<properties>
<module1.version>0.0.2-SNAPSHOT</module1.version>
</properties>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.0-beta-8</version>
</plugin>
</plugins>
</build>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>nl.test</groupId>
<artifactId>release-module1</artifactId>
<version>${module1.version}</version>
</dependency>
</dependencies>
</dependencyManagement>
<scm>
<connection>scm:svn:https://****/svn/repos/tests/trunk/</connection>
</scm>
</project>
{code}
After:
{code:xml}
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>nl.test</groupId>
<artifactId>release-test</artifactId>
<packaging>pom</packaging>
<name>Test Releases</name>
<version>0.0.3-SNAPSHOT</version>
<modules>
<module>release-module1</module>
</modules>
<properties>
<module1.version>0.0.2</module1.version>
</properties>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.0-beta-8</version>
</plugin>
</plugins>
</build>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>nl.test</groupId>
<artifactId>release-module1</artifactId>
<version>${module1.version}</version>
</dependency>
</dependencies>
</dependencyManagement>
<scm>
<connection>scm:svn:https://****/svn/repos/tests/trunk/</connection>
</scm>
</project>
{code}
was (Author: jajansen):
Before
{code:xml}
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>nl.test</groupId>
<artifactId>release-test</artifactId>
<packaging>pom</packaging>
<name>Test Releases</name>
<version>0.0.2-SNAPSHOT</version>
<modules>
<module>release-module1</module>
</modules>
<properties>
<module1.version>0.0.2-SNAPSHOT</module1.version>
</properties>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.0-beta-8</version>
</plugin>
</plugins>
</build>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>nl.test</groupId>
<artifactId>release-module1</artifactId>
<version>${module1.version}</version>
</dependency>
</dependencies>
</dependencyManagement>
<scm>
<connection>scm:svn:https://****/svn/repos/tests/trunk/</connection>
</scm>
</project>
{code}
After:
{code:xml}
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>nl.test</groupId>
<artifactId>release-test</artifactId>
<packaging>pom</packaging>
<name>Test Releases</name>
<version>0.0.3-SNAPSHOT</version>
<modules>
<module>release-module1</module>
</modules>
<properties>
<module1.version>0.0.2</module1.version>
</properties>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.0-beta-8</version>
</plugin>
</plugins>
</build>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>nl.test</groupId>
<artifactId>release-module1</artifactId>
<version>${module1.version}</version>
</dependency>
</dependencies>
</dependencyManagement>
<scm>
<connection>scm:svn:https://****/svn/repos/tests/trunk/</connection>
</scm>
</project>
{code}
> release doesn't bump versions in properties to the next dev iteration
> ---------------------------------------------------------------------
>
> Key: MRELEASE-297
> URL: http://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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
Posted by "Christian Schulte (JIRA)" <ji...@codehaus.org>.
[ 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] Commented: (MRELEASE-297) release doesn't bump versions in
properties to the next dev iteration
Posted by "Martin Zeltner (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206779#action_206779 ]
Martin Zeltner commented on MRELEASE-297:
-----------------------------------------
Hi
It affects also version 2.0-beta-9
Further the version xml element of "release-module1" is changed from "<version>${module1.version}</version>" to the fixed version "0.0.3-SNAPSHOT".
Cheers
Martin
> release doesn't bump versions in properties to the next dev iteration
> ---------------------------------------------------------------------
>
> Key: MRELEASE-297
> URL: http://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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
Posted by "Marc von Renteln (JIRA)" <ji...@codehaus.org>.
[ 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] Commented: (MRELEASE-297) release doesn't bump versions in
properties to the next dev iteration
Posted by "Jan Arend Jansen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158963#action_158963 ]
Jan Arend Jansen commented on MRELEASE-297:
-------------------------------------------
Also affects 2.0-beta8
> release doesn't bump versions in properties to the next dev iteration
> ---------------------------------------------------------------------
>
> Key: MRELEASE-297
> URL: http://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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-297) release doesn't bump versions in
properties to the next dev iteration
Posted by "Martin Todorov (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269988#action_269988 ]
Martin Todorov commented on MRELEASE-297:
-----------------------------------------
Would be great to have this!
> release doesn't bump versions in properties to the next dev iteration
> ---------------------------------------------------------------------
>
> Key: MRELEASE-297
> URL: http://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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
Posted by "Martin Todorov (JIRA)" <ji...@codehaus.org>.
[ 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] Issue Comment Edited: (MRELEASE-297) release doesn't bump
versions in properties to the next dev iteration
Posted by "Jan Arend Jansen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158964#action_158964 ]
Jan Arend Jansen edited comment on MRELEASE-297 at 12/22/08 9:17 AM:
---------------------------------------------------------------------
Before
{code:xml}
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>nl.test</groupId>
<artifactId>release-test</artifactId>
<packaging>pom</packaging>
<name>Test Releases</name>
<version>0.0.2-SNAPSHOT</version>
<modules>
<module>release-module1</module>
</modules>
<properties>
<module1.version>0.0.2-SNAPSHOT</module1.version>
</properties>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.0-beta-8</version>
</plugin>
</plugins>
</build>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>nl.test</groupId>
<artifactId>release-module1</artifactId>
<version>${module1.version}</version>
</dependency>
</dependencies>
</dependencyManagement>
<scm>
<connection>scm:svn:https://****/svn/repos/tests/trunk/</connection>
</scm>
</project>
{code}
After:
{code:xml}
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>nl.test</groupId>
<artifactId>release-test</artifactId>
<packaging>pom</packaging>
<name>Test Releases</name>
<version>0.0.3-SNAPSHOT</version>
<modules>
<module>release-module1</module>
</modules>
<properties>
<module1.version>0.0.2</module1.version>
</properties>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.0-beta-8</version>
</plugin>
</plugins>
</build>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>nl.test</groupId>
<artifactId>release-module1</artifactId>
<version>${module1.version}</version>
</dependency>
</dependencies>
</dependencyManagement>
<scm>
<connection>scm:svn:https://****/svn/repos/tests/trunk/</connection>
</scm>
</project>
{code}
was (Author: jajansen):
Before
{code:xml}
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>nl.test</groupId>
<artifactId>release-test</artifactId>
<packaging>pom</packaging>
<name>Test Releases</name>
<version>0.0.2-SNAPSHOT</version>
<modules>
<module>release-module1</module>
</modules>
<properties>
<module1.version>0.0.2-SNAPSHOT</module1.version>
</properties>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.0-beta-8</version>
</plugin>
</plugins>
</build>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>nl.test</groupId>
<artifactId>release-module1</artifactId>
<version>${module1.version}</version>
</dependency>
</dependencies>
</dependencyManagement>
<scm>
<connection>scm:svn:https://****/svn/repos/tests/trunk/</connection>
</scm>
</project>
{code:xml}
After:
{code:xml}
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>nl.test</groupId>
<artifactId>release-test</artifactId>
<packaging>pom</packaging>
<name>Test Releases</name>
<version>0.0.3-SNAPSHOT</version>
<modules>
<module>release-module1</module>
</modules>
<properties>
<module1.version>0.0.2</module1.version>
</properties>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.0-beta-8</version>
</plugin>
</plugins>
</build>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>nl.test</groupId>
<artifactId>release-module1</artifactId>
<version>${module1.version}</version>
</dependency>
</dependencies>
</dependencyManagement>
<scm>
<connection>scm:svn:https://****/svn/repos/tests/trunk/</connection>
</scm>
</project>
{code:xml}
> release doesn't bump versions in properties to the next dev iteration
> ---------------------------------------------------------------------
>
> Key: MRELEASE-297
> URL: http://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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.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
Posted by "Christian Schulte (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] (MRELEASE-297) release doesn't bump versions in properties
to the next dev iteration
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ 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