You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@continuum.apache.org by idallas <ia...@yahoo.com> on 2006/11/27 20:32:51 UTC
Re: Continuum tries to checkout artifactId instead of module
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 handle projects with child atrifactIds
that != directory names, Continuum should support that too.
It's definitely a deal-breaker for me personally, and I suspect it would be
for a lot of other users as well.
--ian
Emmanuel Venisse wrote:
>
> 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.
>
--
View this message in context: http://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.
Re: Continuum tries to checkout artifactId instead of module
Posted by Emmanuel Venisse <em...@venisse.net>.
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 handle projects with child atrifactIds
> that != directory names, Continuum should support that too.
>
> It's definitely a deal-breaker for me personally, and I suspect it would be
> for a lot of other users as well.
>
> --ian
>
>
> Emmanuel Venisse wrote:
>> 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.
>>
>