Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Cannot Reproduce
-
Affects Version/s: 2.0-beta-8
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
Description
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
Issue Links
- relates to
-
MRELEASE-325
The release plugin does not keep the variable substitution in the connection/developer url after a release prepare/perform.
-
Activity
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 ?
).
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 ?
seems to work in 2.1-SNAPSHOT and 2.0.