You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Max Powers (JIRA)" <ji...@codehaus.org> on 2009/03/05 18:16:12 UTC
[jira] Created: (MRELEASE-421) overwriting property in version tag,
rather than updating property
overwriting property in version tag, rather than updating property
------------------------------------------------------------------
Key: MRELEASE-421
URL: http://jira.codehaus.org/browse/MRELEASE-421
Project: Maven 2.x Release Plugin
Issue Type: Bug
Affects Versions: 2.0-beta-8
Reporter: Max Powers
I have a multimodule project that has the following dependency setup in one of the poms
<nexus-lvo-plugin.version>1.0.2-SNAPSHOT</nexus-lvo-plugin.version>
<dependency>
<groupId>org.sonatype.nexus.plugins</groupId>
<artifactId>nexus-lvo-plugin</artifactId>
<version>${nexus-lvo-plugin.version}</version>
</dependency>
this nexus-lvo-plugin is in the same reactor build as the module above.
In 2.0-beta-8, rather than simply updating the property w/ the release version, the <version> tag in the dependency is updated
leaving
<dependency>
<groupId>org.sonatype.nexus.plugins</groupId>
<artifactId>nexus-lvo-plugin</artifactId>
<version>1.0.2</version>
</dependency>
which causes me to have to update the pom after release is done. this didn't happen in previous release plugin versions
--
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] Closed: (MRELEASE-421) overwriting property in version tag,
rather than updating property
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MRELEASE-421.
---------------------------------
Resolution: Cannot Reproduce
Assignee: Brett Porter
seems to work in 2.1-SNAPSHOT and 2.0.
> overwriting property in version tag, rather than updating property
> ------------------------------------------------------------------
>
> Key: MRELEASE-421
> URL: http://jira.codehaus.org/browse/MRELEASE-421
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-8
> Reporter: Max Powers
> Assignee: Brett Porter
>
> I have a multimodule project that has the following dependency setup in one of the poms
> <nexus-lvo-plugin.version>1.0.2-SNAPSHOT</nexus-lvo-plugin.version>
> <dependency>
> <groupId>org.sonatype.nexus.plugins</groupId>
> <artifactId>nexus-lvo-plugin</artifactId>
> <version>${nexus-lvo-plugin.version}</version>
> </dependency>
> this nexus-lvo-plugin is in the same reactor build as the module above.
> In 2.0-beta-8, rather than simply updating the property w/ the release version, the <version> tag in the dependency is updated
> leaving
> <dependency>
> <groupId>org.sonatype.nexus.plugins</groupId>
> <artifactId>nexus-lvo-plugin</artifactId>
> <version>1.0.2</version>
> </dependency>
> which causes me to have to update the pom after release is done. this didn't happen in previous release plugin versions
--
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-421) overwriting property in version
tag, rather than updating property
Posted by "Thomas Demande (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=252973#action_252973 ]
Thomas Demande commented on MRELEASE-421:
-----------------------------------------
Tested with 2.1, and, as stated in the description, the release plugin updates the dependency version tag, not the property.
That is especially bad because in this case I do use the value of the property in resources files (here, mvn url for OSGi features descriptors, so having SNAPSHOT is bad ;)).
Tested in release plugin 2.1, with Maven 2.2.1 and 3.0.
Can you tell me if this should really work or reopen this issue ?
> overwriting property in version tag, rather than updating property
> ------------------------------------------------------------------
>
> Key: MRELEASE-421
> URL: http://jira.codehaus.org/browse/MRELEASE-421
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-8
> Reporter: Max Powers
> Assignee: Brett Porter
>
> I have a multimodule project that has the following dependency setup in one of the poms
> <nexus-lvo-plugin.version>1.0.2-SNAPSHOT</nexus-lvo-plugin.version>
> <dependency>
> <groupId>org.sonatype.nexus.plugins</groupId>
> <artifactId>nexus-lvo-plugin</artifactId>
> <version>${nexus-lvo-plugin.version}</version>
> </dependency>
> this nexus-lvo-plugin is in the same reactor build as the module above.
> In 2.0-beta-8, rather than simply updating the property w/ the release version, the <version> tag in the dependency is updated
> leaving
> <dependency>
> <groupId>org.sonatype.nexus.plugins</groupId>
> <artifactId>nexus-lvo-plugin</artifactId>
> <version>1.0.2</version>
> </dependency>
> which causes me to have to update the pom after release is done. this didn't happen in previous release plugin versions
--
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