[
https://issues.apache.org/jira/browse/SCM-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960850#comment-17960850
]
ASF GitHub Bot commented on SCM-196:
------------------------------------
jira-importer commented on issue #486:
URL: https://github.com/apache/maven-scm/issues/486#issuecomment-2964598472
**[Emmanuel
Venisse](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=evenisse)**
commented
Now, if connection isn't define, we choose the developerConnection url even
if connectionType is 'connection'
> scm:update doesn't reuse developerConnection when connection not defined.
> -------------------------------------------------------------------------
>
> Key: SCM-196
> URL: https://issues.apache.org/jira/browse/SCM-196
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: maven-plugin, maven-scm-provider-svn
> Environment: mvn 2.0.4
> scm: 1.0-20060505.091301-5
> svn 1.3.1
> Reporter: Jerome Lacoste
> Assignee: Emmanuel Venisse
> Priority: Major
> Fix For: 1.0-beta-4
>
>
> I am using mvn scm:update in a project without a connection (but with a
> developerConnectino) and scm:update fails:
> [INFO] --------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] --------------------------------------------------------------
> [INFO] Cannot run checkout command :
> Embedded error: Can't load the scm provider.
> You need to define a connectionUrl parameter
> [INFO] --------------------------------------------------------------
> The plugin should use the developerConnection when no connection has been
> defined. Otherwise that forces one to copy the developerConnection into the
> connection one which defeats DRY and the fact that the connection represents
> a read-only element. Not sure if that problem is subversion dependent or not,
> so I selected both the plugin and the svn specific component.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
