The line breaks aren't the problem. I made some progress. I'm still a little 
confused by connectionUrl versus developerConnectionUrl but the following in my 
parent POM file finally worked for me. I never got developerConnectionUrl to 
work and I'm honestly not sure how the property is used by the plugin.

<plugins>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-scm-plugin</artifactId>
                <version>1.3</version>
                <configuration>
                    
<connectionUrl>scm:svn:https://10.6.22.11/svn/icfdev/NE-FIMS/trunk/${project.artifactId}</connectionUrl>
                    <username>${svn.username}</username>
                    <password>${svn.password}</password>
                </configuration>
            </plugin>
        </plugins>


On Feb 24, 2010, at 6:51 PM, Bastian Spanneberg wrote:

> Grant Lewis schrieb:
>> As far as I can tell my configuration is correct, using Maven 2.2.1, scm 1.3 
>> and OS X 10.6.2. The relevant parts of my POM file are included. The tags 
>> are in my parent POM file so I expect the child project to inherit. I don't 
>> really understand the difference between connection and developerConnection 
>> so I set them both.
>> When I try to run mvn scm:checkout on a child project I observe the error 
>> shown below from the plug-in. I also tried adding <connectionUrl> in the 
>> configuration for the plugin but that didn't help, same error. Anyone have 
>> some ideas? I'm not having any problems with command-line svn, only the 
>> Maven svn integration. Thanks.
> 
> are these line breaks also in your pom, or just in this mail ? i remember 
> i've got problems once with a similar situation, just cannot remember if it 
> was with a scm connection url.
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to