[jira] [Commented] (SCM-845) Maven Release Plugin releases SNAPSHOT instead of STABLE version (jgit)

["Konrad Windszus (JIRA)" <ji...@apache.org>]

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

Konrad Windszus commented on SCM-845:
-------------------------------------

I have the same issue and seems indeed occur in case when the released artifact is not in the root of the repository (similar to SCM-740). I fail to see how a fix being applied for SCM-740 could be easily transferred to https://github.com/apache/maven-scm/blob/master/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-jgit/src/main/java/org/apache/maven/scm/provider/git/jgit/command/status/JGitStatusCommand.java.

 [~struberg] Since you came up with the original fix for SCM-740, could you have a look what needs to be changed in the JGitFlow provider to support that use case as well?

> Maven Release Plugin releases SNAPSHOT instead of STABLE version (jgit)
> -----------------------------------------------------------------------
>
>                 Key: SCM-845
>                 URL: https://issues.apache.org/jira/browse/SCM-845
>             Project: Maven SCM
>          Issue Type: Bug
>          Components: maven-scm-provider-jgit
>    Affects Versions: 1.9.5
>            Reporter: Archimedes Trajano
>
> I just tried to do a release with the exact scenario as SCM-740 and had the same result.  The SCM-740 provided a fix for gitexe which I verified works when I switched to that provider, but jgit has the same issue



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)