You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "farhan sarwar (JIRA)" <ji...@codehaus.org> on 2008/08/28 21:56:49 UTC
[jira] Commented: (MRELEASE-217) BUILD FAILURE: The version could
not be updated: ${version}
[ http://jira.codehaus.org/browse/MRELEASE-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=146334#action_146334 ]
farhan sarwar commented on MRELEASE-217:
----------------------------------------
I am facing a similar issue, where i get this exception "org.apache.maven.BuildFailureException: The version could not be updated: ${productname.xyz.version}, this is a version property i have defined in my room pom (and being used in child poms) defines the version of the current product/project heirarchy, and instead of using project.version everywhere i have defined this...
> 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
> Assignee: Emmanuel Venisse
> Priority: Critical
> Fix For: 2.0-beta-6
>
> 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