waffel’s Weblog

Februar 16, 2010

howto disable inherited maven plugin

Filed under: software — Thomas Wabner @ 3:43 pm
Tags: , , , ,

We using in our department a big hierarchy of maven parents (like the apache community does). Some of these parents define useful plugins.

If I want to use the parents (and often this is a good idea, because the parents defining for example version informations for my dependencies), but I do not want to have a specific plugin invoked while I’am using maven, I can simple disable the plugin with follow configuration in my pom.xml:

...
<build>
  <plugins>
     <plugin>
        <artifactId>thePluginArtifact</artifactId>
        <groupId>thePluginGroup</groupId>
        <executions>
           <execution>
              <id>the-execution-id</id>
              <phase>none</phase>
           </execution>
        </executions>
     </plugin>
  </plugins>
</build>
...

The trick how to disable a plugin is to set the phase of the plugin to none.

3 Kommentare »

  1. Nice one. I was baffled by these lines in one of the pom files. now I understand that we don’t want the inherited aspectj plugin to weave aspects into our code in that particular module 🙂 thanks!

    Kommentar von Peter Perhac — April 27, 2011 @ 5:25 pm | Antworten

  2. Is this documented anywhere? Or would „foobar“ also work?

    Kommentar von Laird Nelson — Mai 4, 2011 @ 2:19 am | Antworten

  3. […] Details provided from here. […]

    Pingback von thekua.com@work » Another maven workaround – Disabling parent defined plugins from running — Juni 8, 2011 @ 4:46 pm | Antworten


RSS feed for comments on this post. TrackBack URI

Hinterlasse einen Kommentar

Bloggen auf WordPress.com.