Hello Martin,
as a hack you may override this in your pluginManagement by specifying
an invalid phase.
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-source-plugin</artifactId>
<version>${maven-source-plugin.version}</version>
<inherited>true</inherited>
<executions>
<!-- suppress seperate generation of sources-jar during
run of release:stage, see
http://blog.peterlynch.ca/2010/05/maven-how-to-prevent-generate-sources.html
-->
<execution>
<id>attach-sources</id>
<phase>DISABLE_FORKED_LIFECYCLE_MSOURCES-13</phase>
</execution>
<execution>
<id>default-jar-no-fork</id>
<goals>
<goal>jar-no-fork</goal>
</goals>
</execution>
</executions>
</plugin>
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/
On Wed, Dec 2, 2015 at 9:57 PM, Martin Gainty <[email protected]> wrote:
> Folks-
> is there any way to disable a particular plugin (which is somehow declared as
> a default plugin for that phase )from executing in that phase?
>
> Thanks!
> Martin
> ______________________________________________
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
