Re: Continuum tries to checkout artifactId instead of module

[Brett Porter <br...@gmail.com>]

I've been bitten by Continuum stubbornly honouring the SCM URL in the
POM above all else before too.

Apart from reading it on initial import, for the modules and after
updates do you think we should change it to use the real SCM URL and
produce a build warning if the POM differs instead?

- Brett

On 30/08/06, Emmanuel Venisse <em...@venisse.net> wrote:
> 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. rename your directory to the artifactId
> 2. Add the scm url in all your child pom
>
> I prefer 1.
>
> Emmanuel
>
> Matt Raible a écrit :
> > 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 artifactId instead of just using the directories under
> > the parent.  For example, here's the error I get for the first module:
> >
> > Provider message: The svn command failed.
> > Command output:
> > -------------------------------------------------------------------------------
> >
> > svn: URL
> > 'https://appfuse.dev.java.net/svn/appfuse/trunk/appfuse-data-common'
> > doesn't exist
> > -------------------------------------------------------------------------------
> >
> >
> > Why doesn't it just re-use trunk/data/common - that's what's specified
> > in the root-level pom.xml for this artifact?
> >
> > Thanks,
> >
> > Matt
> >
> >
> >
>
>


-- 
Apache Maven - http://maven.apache.org
"Better Builds with Maven" book - http://library.mergere.com/