[#SCM-196] scm:update doesn't reuse developerConnection when connection not defined.

Maven SCM

scm:update doesn't reuse developerConnection when connection not defined.

Created: 09/May/06 05:21 AM Updated: 16/May/06 10:23 AM

Component/s:

maven-scm-provider-svn, maven-plugin

Affects Version/s:

None

Fix Version/s:

1.0-beta-4

Time Tracking:

Not Specified

Environment:

« Hide

mvn 2.0.4
scm: 1.0-20060505.091301-5
svn 1.3.1

Complexity:

Intermediate

Description

« Hide

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.

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Emmanuel Venisse - 12/May/06 03:00 AM

You can choose the developerConnection with connectionType parameter

mvn scm:update -DconnectionType=developerConnection

[ Permlink | « Hide ]

Jerome Lacoste - 16/May/06 09:47 AM

I don't see a real explanation of why this automatic fallback shouldn't be implemented. What would that break? Isn't a

Being able to do scm:update whatever the pom contains sounds closer to the maven philosophy to me. So 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

[ Permlink | « Hide ]

Jerome Lacoste - 16/May/06 09:52 AM

[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?

[ Permlink | « Hide ]

Emmanuel Venisse - 16/May/06 10:16 AM

Now, if connection isn't define, we choose the developerConnection url even if connectionType is 'connection'

[ Permlink | « Hide ]

Jerome Lacoste - 16/May/06 10:23 AM

thanks a lot