[
https://issues.apache.org/jira/browse/SCM-845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963365#comment-17963365
]
ASF GitHub Bot commented on SCM-845:
------------------------------------
jira-importer opened a new issue, #1075:
URL: https://github.com/apache/maven-scm/issues/1075
**[Archimedes
Trajano](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=trajano)**
opened
**[SCM-845](https://issues.apache.org/jira/browse/SCM-845?redirect=false)** and
commented
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
---
**Affects:** 1.9.5
**Issue Links:**
- [SCM-740](https://issues.apache.org/jira/browse/SCM-740) Maven Release
Plugin releases SNAPSHOT instead of STABLE version
(_**"is a clone of"**_)
- [SCM-807](https://issues.apache.org/jira/browse/SCM-807) JGit impl
check-in fails unless the Maven project is in the working copy root
1 votes, 3 watchers
> 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 (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-jgit
> Affects Versions: 1.9.5
> Reporter: Archimedes Trajano
> Priority: Major
> Fix For: 2.0.0-M2
>
>
> 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
(v8.20.10#820010)
