You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by mr...@aim.com on 2010/10/13 16:40:41 UTC

multimodul and parent pom question

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

 

 



Re: multimodul and parent pom question

Posted by Justin Edelson <ju...@gmail.com>.
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, mremersoncod@aim.com 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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org