[jira] Closed: (MNG-2208) Failure to checkout M2 module from SVN

["Brett Porter (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MNG-2208?page=all ]
     
Brett Porter closed MNG-2208:
-----------------------------

     Assign To: Brett Porter
    Resolution: Won't Fix

the appending of the artifact ID to the SCM URL is by design.

Workaround is to explictly declare the correct configuration in the child POM.

There is another open bug for improving this in 2.1

> Failure to checkout M2 module from SVN
> --------------------------------------
>
>          Key: MNG-2208
>          URL: http://jira.codehaus.org/browse/MNG-2208
>      Project: Maven 2
>         Type: Bug

>     Versions: 2.0.3
>     Reporter: Felipe Leme
>     Assignee: Brett Porter

>
>
> I have a M2 project with many sub-projects; one of them is the web application, whose directory is called webapp, the module on the parent's pom is also webapp but the project's artifactId is mycompany-web. When I run 'mvn install' from the parent on command line, it works fine; when I import the parent's pom into continuum, it works fine also (i.e., it automatically set the sub-projects). But continuum fails to build the webapp project with the message:
> Provider message: The svn command failed.
> Command output: 
> -------------------------------------------------------------------------------
> svn: URL 'http://svn.versiondude.net/mycompany/voxblue/trunk/mycompany-web' doesn't exist
> In other words, continuum created the wrong URL: it used the sub-project's artifactId and not the name defined on the parent's POM (I'm not sure if that's a bug on continuum or M2, but the fact is that either both should work or both fail).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira