[
http://jira.codehaus.org/browse/MRELEASE-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93657
]
David Hoffer commented on MRELEASE-217:
---------------------------------------
I tried that and it skips it, here is the log:
23:20:16]: Ignoring artifact version update for expression: ${project.version}
Now maybe I didn't understand what this means. I thought it was not
understanding what to do so it was skipped. Are you saying that keeping
${project.version} in the version tag is what maven prefers and it will know
what this means (always replace with this artifacts version)?
Or is it better to use ${version} and have it replaced with the actual version
in the POM? Which is the more correct behavior?
-dh
> BUILD FAILURE: The version could not be updated: ${version}
> -----------------------------------------------------------
>
> Key: MRELEASE-217
> URL: http://jira.codehaus.org/browse/MRELEASE-217
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-5
> Environment: XP Pro SP2
> Reporter: David Hoffer
> Priority: Critical
> Attachments: buildlog.txt, poms-for-release-plugin.zip
>
>
> 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:
--
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
