[jira] [Commented] (MRELEASE-1126) maven-release-plugin ignores pinned maven-deploy-plugin version

["Graham Leggett (Jira)" <ji...@apache.org>]

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

Graham Leggett commented on MRELEASE-1126:
------------------------------------------

Figured out what triggered this.

The branch the project belongs to exists in two places, one place is the pom itself, the second place is known to the underlying version control (in my case svn, but this will affect git, etc).

The release plugin appears to be choosing arbitrarily between these two separate values for tasks like creating branches and tags, leading to weirdness like this when the branch that the underlying version control sees, and the branch in the POM, don't match.

We need a simple sanity check - if the branch that's checked out according to the underlying version control does not match the branch value in the POM, exit with an error and don't continue. This should be one of the very first sanity checks, alongside the "is anything not-checked-in" check.

With the two values forced to be the same, it no longer matters if the two values are confused.


> maven-release-plugin ignores pinned maven-deploy-plugin version
> ---------------------------------------------------------------
>
>                 Key: MRELEASE-1126
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-1126
>             Project: Maven Release Plugin
>          Issue Type: Bug
>          Components: perform
>    Affects Versions: 3.0.0
>            Reporter: Graham Leggett
>            Priority: Major
>             Fix For: waiting-for-feedback
>
>
> When attempting to perform a release, the deploy plugin triggered by the release plugin fails, due to a long since fixed bug in the deploy plugin.
> While the pom has deploy plugin v3.1.1 pinned, the release plugin attempts to use v2.7 of the deploy plugin.
> The release plugin appears to be using different plugin versions in the release:perform goal as the actual project, making releases very difficult.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)