You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Dave Moten (JIRA)" <ji...@codehaus.org> on 2013/04/19 02:29:53 UTC

[jira] (MRELEASE-799) update-versions fails when the project artifact is used with a version other than the current snapshot

    [ https://jira.codehaus.org/browse/MRELEASE-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=323918#comment-323918 ] 

Dave Moten commented on MRELEASE-799:
-------------------------------------

this looks to still be an issue for release-plugin 2.3.2. I noticed that a workaround is to place explicit versions where you used  ${lastReleasedProjectVersion}.
                
> update-versions fails when the project artifact is used with a version other than the current snapshot
> ------------------------------------------------------------------------------------------------------
>
>                 Key: MRELEASE-799
>                 URL: https://jira.codehaus.org/browse/MRELEASE-799
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: update-versions
>    Affects Versions: 2.3.2
>         Environment: maven 2.2.1, maven 3.0.3
>            Reporter: Peter Miklos
>
> If a maven project uses its own artifact eg. as a dependency of a plugin with a version other than the current snapshot then release:update-versions will fail with an error like this:
> bq. The artifact (com.example:test) requires a different version (3.1.50) than what is found (3.1.49) for the expression (lastReleasedProjectVersion) in the project (com.example:test)
> Basically, the latest release of the same artifact is used for some sort of regression testing and it seems that the update-versions, after moving to the next release version from snapshot, notices that there is a discrepancy between the new release version and the version used as a plugin dependency.
> This error popped up when I started to use release plugin 2.2.2 and as a result of MRELEASE-412 the properties used in the version tag are also updated.
> I think the update-versions should remember which artifacts have been updated from snapshot to the new release version, and then check those only.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira