RE: Adding extra modules to parent pom does not create an extra project in continuum
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 any notifiers. Speaking of definitions, adding support for build definitions in the pom.xml CI configuration for continuum would be ideal. It would make re-adding whole trees much more palatable, since less manual re-configuration would be necessary. Christian. christian gruber + agile coach and architect Israfil Consulting Services Corporation email [EMAIL PROTECTED] + bus +1 (905) 640-1119 cell: +1 (416) 998-6023 + cell: +1 (410) 900-0796
Re: Adding extra modules to parent pom does not create an extra project in continuum
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 for dependencies. I have been removing the version identified as this is now in the dependencyManagement section of the parent pom. 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 dependencyManagement section? 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 readd the parent. So you are saying that adding the module should work correctly. I will look into it more. Is there any plans to change this? It would ideally be nice if any time new modules were found, they were just added in the same fashion continuum adds them when it initially loads a multi-module pom. On a large project, it can be hard to keep up sometimes with new modules that get created. Thanks, Baron
Re: Adding extra modules to parent pom does not create an extra project in continuum
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 dependencyManagement section? Yes the parent pom is in both the internal repository and the local repository. (I already had one module working fine, I was adding the second)
Adding extra modules to parent pom does not create an extra project in continuum
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 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). If I delete the parent project and then re-add the pom file it correctly adds the parent and the new modules. What is the correct way to get another module included in the build? Thanks Bae
Re: Adding extra modules to parent pom does not create an extra project in continuum
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 subdirectories. This would lead me to prefer the flat approach of: ROOT - parent/pom.xml - module1/pom.xml - module2/pom.xml As it would checkout only the bits that are needed.
