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

ASF GitHub Bot commented on SCM-88:
-----------------------------------

jira-importer commented on issue #329:
URL: https://github.com/apache/maven-scm/issues/329#issuecomment-2964585992

   **[Wim 
Deblauwe](https://issues.apache.org/jira/secure/[email protected])**
 commented
   
   I voted for this, because you don't release every day, and I found out how 
easy I forgot to pass that option, so this improvement would be very welcome.
   




> Add transparent support for locking providers
> ---------------------------------------------
>
>                 Key: SCM-88
>                 URL: https://issues.apache.org/jira/browse/SCM-88
>             Project: Maven SCM (Moved to GitHub Issues)
>          Issue Type: Improvement
>          Components: maven-scm-api
>    Affects Versions: 1.0-beta-2
>            Reporter: Mike Perham
>            Assignee: Emmanuel Venisse
>            Priority: Major
>             Fix For: 1.0-beta-2
>
>         Attachments: release-plugin.txt, scm.txt
>
>
> Currently the release plugin requires a command line parameter "useEditMode" 
> to work with the Clearcase and Perforce providers.  Please integrate the 
> notion of locking vs non-locking providers into the SCM API so this does not 
> need to be passed on the command line.



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

Reply via email to