maven2: how to share a plugin configuration between parent and children pom?

Question

I'm trying to reduce copy/pasting in our maven pom files.

We have one master pom and many children projects pom inheriting from the master.

I want to share a complex plugin definition looking like:

<plugins>
    ...
    <plugin>
        <groupId>org.codehaus.mojo</groupId>
        <artifactId>appassembler-maven-plugin</artifactId>
        <configuration>
            <!-- many xml lines here --> 
        </configuration>

        <executions>
            <execution>
                <phase>package</phase>
                <goals>
                    <goal>assemble</goal>
                    <goal>generate-daemons</goal>
                    <goal>create-repository</goal>
                </goals>
            </execution>
        </executions>

        <dependencies>
            <dependency>
                <groupId>org.codehaus.mojo.appassembler</groupId>
                <artifactId>appassembler-booter</artifactId>
                <version>1.0</version>
            </dependency>
        </dependencies>
    </plugin>
    ...
</plugins>

When this plugin definition is in the project pom, packaging is well done.
When definition is moved to parent pom (in or in ), then the packaging is not even started.

Is it possible to share a plugin configuration ? How ?

-- Edit after first answers---
I have tried the following:
- put my XL packaging plugin config in the element of my parent pom
- add this lines in my project pom in the element:

<plugins>
...
   <plugin>
      <groupId>org.codehaus.mojo</groupId>
      <artifactId>appassembler-maven-plugin</artifactId>
   </plugin>
...
</plugins>

but it is not working... What can be wrong with that ?

-- last edit -- I think I get what was the problem:
the plugin re-use declaration should be declared in a profile build.
I done that in an always enabled plugin and now it is working fine.

Thanks a lot.

score 26 · Accepted Answer · edited Feb 06 '18 at 01:56

26

You could wrap the plugins of the parent in a <pluginManagement> tag.

   <build> 
       <pluginManagement>
           <plugins>
               <plugin> ... </plugin>
           </plugins>
       </pluginManagement>
   </build>

Children plugins will then inherit the configurations when they declare the plugin in their build tag.

edited Feb 06 '18 at 01:56

Thales Valias

563
5
11

answered Nov 10 '10 at 15:04

John Vint

39,695
7
78
108

I have tried this but it is not working. I have updated my question regarding your answer. – Guillaume Nov 10 '10 at 15:21
1

Run help:effective-pom and see what the plugin configuration looks like. You definitely are using the pluginManagenement though? – John Vint Nov 10 '10 at 15:23
build using the plugin was declared in a profile. So the plugin config should have been declared in a profile too... Thanks for your help. – Guillaume Nov 12 '10 at 10:19

score 2 · Answer 2 · edited Feb 07 '18 at 00:44

Have you tried using the plugin management feature of Maven? It'll allow you to push that configuration information down to the children pom.xml files from the parent pom.xml:

   <build> 
       <pluginManagement>
           <plugins>
               <plugin>your_plugin</plugin>
           </plugins>
       </pluginManagement>
   </build>

Now, not all plugins are as well done as those from the org.apache.maven.plugins group. It may be necessary to move your configuration section in between your execution elements.

maven2: how to share a plugin configuration between parent and children pom?

2 Answers2

Linked