It wasn't a bug but a known limitation in maven inheritance in child pom. I
implemented a workaround in continuum and will be available in 1.1
Emmanuel
idallas a écrit :
Is this issue considered a bug, or a known limitation? (I didn't find
anything in Jira)
It seems like if Maven is able to h
p://www.nabble.com/Continuum-tries-to-checkout-artifactId-instead-of-module-tf2186430.html#a7566347
Sent from the Continuum - Users mailing list archive at Nabble.com.
This pb is a maven pb when directory name isn't equals to the artifactId. In your case, the
directory is data and artifactId is appfuse-data
You can check the scm url resolution in your child pom with this command 'mvn
help:effective-pom'
you can choose between two solutions for this pb.
1. re
Since I've got most of AppFuse ported to Maven 2, I decided to give
Continuum a try today. I used the following URL for my pom.xml:
https://appfuse.dev.java.net/source/browse/*checkout*/appfuse/trunk/pom.xml
Continuum finds all the projects from my pom.xml files, but it tries
to checkout the ar
