[
https://issues.apache.org/jira/browse/SCM-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17959958#comment-17959958
]
ASF GitHub Bot commented on SCM-57:
-----------------------------------
jira-importer commented on issue #290:
URL: https://github.com/apache/maven-scm/issues/290#issuecomment-2964583609
**[John
Didion](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jdidion)**
commented
1. New base class for scm provider repositories. This one is for
server-based repositories, specically Perforce, CVS, and Starteam.
2. Modified the abstract Mojo to configure server-based repository providers
from \<server> entries in the settings, if they exist. It assumes the server
IDs are host:port.
3. Modified the Perforce checkout command to look in the server properties
for client spec name first before looking for a system property.
> m2 maven-scm-plugin should use the same configurations/properties with M1
> plugin
> --------------------------------------------------------------------------------
>
> Key: SCM-57
> URL: https://issues.apache.org/jira/browse/SCM-57
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-plugin
> Affects Versions: 1.0-alpha-3
> Environment: xp
> Reporter: Dan Tran
> Assignee: Emmanuel Venisse
> Priority: Major
> Attachments: AbstractScmMojo.java, PerforceCheckOutCommand.java,
> ServerBasedScmProviderRepository.java
>
>
> I think m2 should try to make scm plugin configuration compatible with m2
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
