I have a setup where most of my projects require the xtend plugin to be run both for the compile and testCompile goals. I describe it in a pluginManagement section:
Generally, you can only disables executions with a trick:
Set the executions phase to non existant phase (dont-execute
). Note however, that you have to use two different execution ids to allow both goals to be individually turned off:
org.eclipse.xtend
xtend-maven-plugin
2.5.3
xtend-compile
compile
testCompile
xtend-testCompile
testCompile
Submodule:
org.eclipse.xtend
xtend-maven-plugin
2.5.3
xtend-testCompile
dont-execute
In your specific case, you could, of course, also use the skipXtend
configuration property in each execution to not skip the execution, but only prevent the plugin from doing anything:
org.eclipse.xtend
xtend-maven-plugin
2.5.3
xtend-testCompile
xtend-testCompile