Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
2.0-beta-5
-
None
-
None
-
XP Pro SP2
Description
I manually built 2.0-beta-5 from maven-release-1 tag because of bug in 2.0-beta-4. I have found a problem using 2.0-beta-5 with a large multi-module project which makes heavy use of ${version} macros. This macro is used for the version for any dependency on modules within each module. For example in one module where I have a dependency on 3 other modules I have this:
<dependencies>
<dependency>
<groupId>com.xrite</groupId>
<artifactId>xdsiii-driver-api</artifactId>
<version>${version}</version>
</dependency>
<dependency>
<groupId>com.xrite</groupId>
<artifactId>xdsiii-driver</artifactId>
<version>${version}</version>
</dependency>
<dependency>
<groupId>com.xrite</groupId>
<artifactId>xdsiii-instrument-dtp22</artifactId>
<version>${version}</version>
</dependency>
When I run the prepare phase I get the following error:
[INFO] Transforming 'X-Rite XDSIII Instrument Drivers'...
[INFO] Transforming 'X-Rite XDSIII Base Instrument'...
[INFO] Transforming 'X-Rite XDSIII DTP22 Instrument'...
[INFO] Updating xdsiii-instrument-base to 1.84
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] The version could not be updated: ${version}
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.BuildFailureException: The version could not be updated: ${version}
It starts updating the poms with the new release version and then fails part way through the process.
I will attach some files:
Attachments
Attachments
Issue Links
- relates to
-
MRELEASE-666 release:prepare can fail during rewrite-poms-for-development phase if a property matches the version being released
- Closed