continuum-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Edward Gruber <>
Subject Re: [Multiple modules]
Date Tue, 26 Sep 2006 00:40:51 GMT
Yeah.  There's a ticket in the maven JIRA about it, proposing that
${parentSCMUrl}/${modulePath} be used instead of
${parentSCMUrl}/${artifactId}.  No notion of whether it will be actually
accepted and implemented.

The proper workaround is to explicitly define SCM urls in each child
project, as I believe was mentioned earlier, or to make your sub-project
modules under the parent and make the folder name equal to the artifactId. 

This is, however, really problematic for working with maven and eclipse
simultaneously, as you can't get the full project set, including parent,
loaded in eclipse, because eclipse cannot support sub-projects nested in
other projects.


David Roussel wrote:
> That does seem to be the convention in Maven (it's not a continuum
> thing), that the modules are most often in subfolders of the parent
> project, and have folder names the same as the project name.
> On Mon, 25 Sep 2006 14:07:01 +0200, "Francois Le Fevre"
> <> said:
>> Dear all,
>> I have identified my error: it seems that module and parent artifact id 
>> have to match to the folder name when using subversion and continuum!
>> Could you please confirm the convention?
>> Francois
>> snip


*christian** gruber + process coach and architect*

*Israfil Consulting Services Corporation*

*email** + bus 905.640.1119 + mob 416.998.6023*

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message