maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mortagne (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (MRELEASE-799) update-versions fails when the project artifact is used with a version other than the current snapshot
Date Tue, 21 Aug 2018 13:13:00 GMT

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

Thomas Mortagne edited comment on MRELEASE-799 at 8/21/18 1:12 PM:
-------------------------------------------------------------------

I confirm the issue is still there in 2.5.3.

I get the following when trying to use release:branch goal:

{noformat}
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5.3:branch
(default-cli) on project xwiki-platform: The version could not be updated: ${upgradetest.previousdata.version}
-> [Help 1]
{noformat}

(this is the release:branch error that's probably why it's a bit different from the one in
the issue description)

when the release plugin hits https://github.com/xwiki/xwiki-platform/blob/0e0c1c3ee521f6fb19262e0992c2964bba207bca/xwiki-platform-distribution/xwiki-platform-distribution-flavor/xwiki-platform-distribution-flavor-test/xwiki-platform-distribution-flavor-test-upgrade/xwiki-platform-distribution-flavor-test-upgrade-911/pom.xml#L41.

Using 9.11.7 instead of the variable works as a workaround but I would really prefer to not
duplicate things as much as possible.

I attached a simpler project to reproduce the issue ("ko/" fails and "ok/" has the workaround
with direct version).


was (Author: tmortagne):
I confirm the issue is still there.

I get the following when trying to use release:branch goal:

{noformat}
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5.3:branch
(default-cli) on project xwiki-platform: The version could not be updated: ${upgradetest.previousdata.version}
-> [Help 1]
{noformat}

(this is the release:branch error that's probably why it's a bit different from the one in
the issue description)

when the release plugin hits https://github.com/xwiki/xwiki-platform/blob/0e0c1c3ee521f6fb19262e0992c2964bba207bca/xwiki-platform-distribution/xwiki-platform-distribution-flavor/xwiki-platform-distribution-flavor-test/xwiki-platform-distribution-flavor-test-upgrade/xwiki-platform-distribution-flavor-test-upgrade-911/pom.xml#L41.

Using 9.11.7 instead of the variable works as a workaround but I would really prefer to not
duplicate things as much as possible.

I attached a simpler project to reproduce the issue ("ko/" fails and "ok/" has the workaround
with direct version).

> update-versions fails when the project artifact is used with a version other than the
current snapshot
> ------------------------------------------------------------------------------------------------------
>
>                 Key: MRELEASE-799
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-799
>             Project: Maven Release Plugin
>          Issue Type: Bug
>          Components: update-versions
>    Affects Versions: 2.3.2
>         Environment: maven 2.2.1, maven 3.0.3
>            Reporter: Péter Miklós
>            Priority: Major
>         Attachments: MRELEASE-799.zip
>
>
> 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 was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message