[
https://issues.apache.org/jira/browse/SCM-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17959960#comment-17959960
]
ASF GitHub Bot commented on SCM-57:
-----------------------------------
jira-importer commented on issue #290:
URL: https://github.com/apache/maven-scm/issues/290#issuecomment-2964583608
**[John
Didion](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jdidion)**
commented
Why can't we just generalize the mecahnism now used for svn and starteam,
i.e. using the \<server> settings in settings.xml for provider-specific config?
I'm specifically interested in perforce, so I'm going to go ahead and patch
the plugin for that particular provider.
> 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)
