Hi Dario, I had this problem too. The solution is to declare the scm url in every pom, not just in the parent one. Maven provides a java method for a project which returns its scm url. If there is no explicit scm url declared in the project, it uses the one from the parent and appends the project's artifactid. There isn't much else that maven could do. Possibly Continuum could override the scm url returned by a child module, as it knows the parent url, and the relative path from parent to child as declared in the parent's <module> declaration; that seems a little tricky to me though. And as noted above, declaring the scm path in every pom solves the issue. Regards, Simon
_____ From: Dário Oliveros [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 24, 2006 3:33 AM To: continuum-users@maven.apache.org Subject: Problem when adding a m2 project into continuum I am having trouble importing a multiproject pom.xml that has its modules located in a different directory structure. Please see below: main/ trunk/ pom.xml (multiproject) components/ comp_1/ trunk/ pom.xml ... comp_n/ trunk/ pom.xml multiproject pom.xml: ... components/comp_1 ... components/comp_n So If I import /main/trunk/pom.xml, continuum tries to find the modules as subdirectories under main/trunk. I brought up this scenario since I use svn:externals in the main/trunk and had no problem when checking out the entire project from svn. However, I got stuck with continnum now :-( I think it would be great to have a feature where you could decide whether to import the entire multiproject (with all modules) or just the multiproject itself. Any comments or suggestions would be appreciated. Dário -- View this message in context: http://www.nabble.com/Problem+when+adding+a+m2+project+into+continuum-t16696 51.html#a4525221 Sent from the Continuum - Users forum at Nabble.com.
