maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jerome Lacoste (JIRA)" <>
Subject [jira] Commented: (SCM-196) scm:update doesn't reuse developerConnection when connection not defined.
Date Tue, 16 May 2006 14:53:41 GMT
    [ ] 

Jerome Lacoste commented on SCM-196:

[accidently fired the form in the middle of my former comment. Here it is, completed]

Sorry but I am not satisfied. Having to remember if project a project defines a non developer
connection or not is counter intuitive.

I don't see a real explanation of why this automatic fallback shouldn't be implemented. What
would that break? Isn't a read-write connection also a read connection? Being able to do scm:update
whatever the pom contains sounds closer to the maven philosophy to me. So to me, there should
be an automatic fallback mecanism.

If fallback by default is not an option, consider something like

mvn scm:update -DconnectionType=fallback

As long as I can put this default option somewhere in my maven config and not have to type
it again, I will be satisfied. Would something like that be OK?

> scm:update doesn't reuse developerConnection when connection not defined.
> -------------------------------------------------------------------------
>          Key: SCM-196
>          URL:
>      Project: Maven SCM
>         Type: Improvement

>   Components: maven-scm-provider-svn, maven-plugin
>  Environment: mvn 2.0.4
> scm: 1.0-20060505.091301-5
> svn 1.3.1
>     Reporter: Jerome Lacoste
>     Assignee: Emmanuel Venisse

> I am using mvn scm:update in a project without a connection (but with a developerConnectino)
and scm:update fails:
> [INFO] --------------------------------------------------------------
> [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 is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message