maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marcos Mendez <>
Subject Re: import plugin configurations
Date Fri, 04 Jan 2013 21:30:41 GMT
I found this approach at
Maybe the name is not correct, but I want a pom with most configurations that I can import
from all my separate projects. Works for dependencies, though I have to define a separate
process to actually import the properties from that pom. I just want to have the plugin configurations
come from one place.

On Jan 4, 2013, at 4:25 PM, Marcos Mendez wrote:

> I actually do mean super pom. We have multiple projects that have similar configurations,
dependencies, plugins, etc.  I don't want to have them repeated each time and they will not
have the same parent - it is not feasible. I've used the import scope for setting dependency
versions (e.g. dependency management) in one place and that worked ok. Has anyone tried to
do this for plugins configurations as well?
> On Jan 4, 2013, at 4:09 PM, Anders Hammar wrote:
>> First, there is only one "super-POM" and that one is included in Maven
>> itself. What you probably mean is a "parent pom".
>> To use that parent pom you declare it in the "parent" section, not as a
>> import scope dependency.
>> /Anders
>> On Fri, Jan 4, 2013 at 10:00 PM, Marcos Mendez <> wrote:
>>> I've defined a superpom and I'm using the import scope in another maven
>>> project to apply those. I'm not seeing the configurations being applied for
>>> the plugins I've defined in the superpom's pluginManagement.
>>> Any ideas?
>>> Regards,
>>> Marcos
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail:
>>> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message