[
https://issues.apache.org/jira/browse/SCM-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960034#comment-17960034
]
ASF GitHub Bot commented on SCM-54:
-----------------------------------
jira-importer commented on issue #304:
URL: https://github.com/apache/maven-scm/issues/304#issuecomment-2964584547
**[Michael
Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)**
commented
This issue has been auto closed because it has been inactive for a long
period of time. If you think this issue still applies, retest your problem with
the most recent version of Maven and the affected component, reopen and post
your results.
> API enhancement for SSCM vendor compatability
> ---------------------------------------------
>
> Key: SCM-54
> URL: https://issues.apache.org/jira/browse/SCM-54
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: maven-scm-api
> Reporter: Mike Esler
> Priority: Major
>
> As discussed on the mailing list, we should add a reserved/uunreserved
> boolean to the checkout command.
> Also, provide a bind() command which binds a local directory to an
> SCM-controlled project. There should be a corresponding release() method as
> well.
> Thus, the calling pattern to get files out of a repository would always be a
> 2-step process:
> bind(localDirectory, remoteProject)
> checkout(localDirectory, fileset, reserved/unreserved)
> This will open the door for integrations with a lot of SCM vendors, and allow
> us to clean up the SCM provider in the Wagon code.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
