[
https://issues.apache.org/jira/browse/SCM-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17962745#comment-17962745
]
ASF GitHub Bot commented on SCM-725:
------------------------------------
jira-importer commented on issue #931:
URL: https://github.com/apache/maven-scm/issues/931#issuecomment-2964633833
**[Chris
Graham](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=chrisgwarp)**
commented
I've investigated this. It is actually an error in the release
plugin/manager. It never calls the unlock scm apis.
Congratulations. You're the first person on the planet to use this
functionality! :)
I've created https://issues.apache.org/jira/browse/MRELEASE-904 to track.
This issue is not specific to the jazz provider, it applies to all providers
as it's all called from the release plugin. That is where it needs to be fixed.
As such, this issue should probably be closed as 'not a bug'.
> Failure to unlock pom.xml on RTC server after release:perform
> -------------------------------------------------------------
>
> Key: SCM-725
> URL: https://issues.apache.org/jira/browse/SCM-725
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-jazz
> Affects Versions: 1.7, 1.8, 1.8.1
> Environment: Windows 7 on client workstation
> RTC 4.0.1
> Reporter: Oscar Picasso
> Assignee: Chris Graham
> Priority: Major
>
> 1- configured maven-release-plugin with
> <useEditMode>true</useEditMode>
> 2- mvn release:prepare => the pom.xml is locked on the RTC server
> 3- mvn release:perform => the pom.xml is still locked on the RTC server. It
> should not.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
