[
https://issues.apache.org/jira/browse/SCM-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960035#comment-17960035
]
ASF GitHub Bot commented on SCM-54:
-----------------------------------
jira-importer commented on issue #304:
URL: https://github.com/apache/maven-scm/issues/304#issuecomment-2964584542
**[Anthony B.
Coates](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=abcoates)**
commented
Please also consider
http://jira.codehaus.org/browse/MPSCM-55#action_46008 [09/Sep/05 07:32 AM]
where I've tried to briefly outline that Maven needs to be able to work with
JARs that don't have versions in the names, so that it can be used effectively
with configuration management tools like ClearCase. Thanks, Cheers, Tony.
> 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)
