You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2015/09/06 22:51:50 UTC
[jira] [Closed] (SCM-54) API enhancement for SSCM vendor
compatability
[ https://issues.apache.org/jira/browse/SCM-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov closed SCM-54.
-----------------------------
Resolution: Auto Closed
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
> Issue Type: Improvement
> Components: maven-scm-api
> Reporter: Mike Esler
>
> 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
(v6.3.4#6332)