Separating aggregation from inheritance is definitely a good idea if your modules are versioned and/or released independently from one another which sounds like is the case here.
Justin On 10/13/10 10:40 AM, [email protected] wrote: > Hi, > > we have a multimodul project with a lot of modules. Currently the root-pom of > the multimodul project is also the parent pom of each submodul project. > This stroke us quite some time when we made changes in the parent pom > regarding dependency versions in dependencyManagement or other configuration > changes, because we could not deploy the pom without building the whole > system. > > So our idea is to separate the two concerns, namely the configurations > (scm/CI server/ dependencyManagement / distributionManagement etc) with the > module information. So the root-pom only has the module information and one > of the modules is a pom project with all configurations. All other modules > use then this pom as their parent. With that we could make changes to the > parent pom without any trouble. > > Is this way correct or will it create more trouble ? > > Thanks for any advice > > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
