> But when adding the module pom I think it is failing to find the
> parent pom (or even looking for it) and gives you an error that the
> version for the dependency is mandatory and missing.
>
Perhaps the parent pom's module has not been 'installed' in continuum's
repository with the dependencyMa
> > > If I try to add the module pom I get an error that it can not find the
> > > dependency version information (since that is specified in the parent
> > > pom).
> >
> > what is the error? How do you define the version in your module?
>
> I am not at work, so this is from memory.
> The error is
>>
>> What is the correct way to get another module included in the build?
>
>add new modules one by one or delete all (parent and sub-modules) and read
>the parent.
This last option is highly frustrating (I've had to do it many times),
because it kills any build definitions you have created, and
Barrie Treloar a écrit :
If I add another module to the parent pom and then rebuild the parent
project in continuum the new module does not get added as another
project.
yes, it isn't supported yet.
If I re-add the pom file via Maven 2.0+ Project link (I am using
file:// urls to do this) I
While I'm discussing this, I notice because I am using the recommended
project layout:
ROOT
- pom.xml
- module1/pom.xml
- moduel2/pom.xml
That to rebuild the ROOT project it takes forever since it has to
checkout the entire CVS tree.
Whereas the module builds only checkout the module subdirector
If I add another module to the parent pom and then rebuild the parent
project in continuum the new module does not get added as another
project.
If I re-add the pom file via Maven 2.0+ Project link (I am using
file:// urls to do this) I get a second parent project but not
sub-modules.
If I try t
