On Fri, 30 Sep 2005, Thomas Van de Velde wrote:
> > > - Check in the entire tree as a single SCM module.
> >
> > Correct. You can also use different scm repositories for each module if
> > you want, as long as you specify the scm repository in the pom for that
> > module.
>
> How could that work? Your master POM is not aware of where in SCM its
> modules are located, right? Or is the master POM looking at the list of
> modules to find a corresponding pom in the repository, and use that SCM info
> to checkout the modules?
The master pom knows it's own location, say $REPO_LOCATION/
Each module defined in that pom will have a scm location of
$REPO_LOCATION/module-name (recursively).
However, i see your problem, if the module you check out is a grandchild
of the root pom. AFAIK there's no <module> traversal done from the root
pom onwards to the section you check out. However, what will work is
if each module has the project defining that module as a parent-pom.
So:
root/pom.xml defines module a, scm location $REPO_LOCATION
a/pom.xml defines module b, parent=root
b/pom.xml defines module c, parent = a
etc..
If you check out b the scm location should be calculated as being
$REPO_LOCATION/a/b/
Since it is good practise to define the parent pom as the pom that defines
the current pom as a module (i.e. b defines a as it's parent since a
defines b as a module), there should be no problem.
Though scm urls are calculated from the grandchild back to the root pom
using the <parent> tags, not the other way around using <module> tags.
-- Kenney
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
