You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Mehdi Hayani <ha...@gmail.com> on 2015/05/28 16:30:08 UTC

Use of one POM parent or many each for a scope

Hello team,


Actually, I'm building a pom parent that all applications under the enitty
where I'm working will have to implement.

The idea is to specify all the dependencies and plugins inside the pom
parent with the version using the dependencyManagement and
pluginManagement, and at the application level, only mention the required
plugin.

Since not all the applications use the same technos, I got the idea of
creating pom parent by scope (for Spring, for JAXRS, ...) and thereafter
include those pom in a global pom parent that will be inherited by each
applications.

I don't know if you've faced this before, but I'm asking which one is
recommended ? using one pom parent that contains declaration of all
dependencies or create mini pom parent by scope and include them in the pom
parent as dependencies ?


hanks in advance for you help.


Regards

Re: Use of one POM parent or many each for a scope

Posted by Ron Wheeler <rw...@artifact-software.com>.
Sounds like you are thinking about something similar to what we use.
Works very well and makes life very easy for developers.

http://blog.artifact-software.com/tech/?p=121


Ron

On 28/05/2015 10:30 AM, Mehdi Hayani wrote:
> Hello team,
>
>
> Actually, I'm building a pom parent that all applications under the enitty
> where I'm working will have to implement.
>
> The idea is to specify all the dependencies and plugins inside the pom
> parent with the version using the dependencyManagement and
> pluginManagement, and at the application level, only mention the required
> plugin.
>
> Since not all the applications use the same technos, I got the idea of
> creating pom parent by scope (for Spring, for JAXRS, ...) and thereafter
> include those pom in a global pom parent that will be inherited by each
> applications.
>
> I don't know if you've faced this before, but I'm asking which one is
> recommended ? using one pom parent that contains declaration of all
> dependencies or create mini pom parent by scope and include them in the pom
> parent as dependencies ?
>
>
> hanks in advance for you help.
>
>
> Regards
>


-- 
Ron Wheeler
President
Artifact Software Inc
email: rwheeler@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org