Skip to main content
aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorIgor Fedorenko2012-11-29 18:30:17 -0500
committerIgor Fedorenko2012-11-29 22:10:59 -0500
commit38f6b83cf3bb54e94ceddeea2233be39f910cc2c (patch)
tree8f2164452c184b6036474e4ab05dddf11eea5bc8 /org.eclipse.m2e.lifecyclemapping.defaults
parentfc5b049d77da08ef617ed27a6bc574e8c1ae8182 (diff)
downloadm2e-core-38f6b83cf3bb54e94ceddeea2233be39f910cc2c.tar.gz
m2e-core-38f6b83cf3bb54e94ceddeea2233be39f910cc2c.tar.xz
m2e-core-38f6b83cf3bb54e94ceddeea2233be39f910cc2c.zip
395433 changed default <runOnIncremental> to false
In order to make m2e less prone to endless workspace builds, <execute/> lifecycle mapping will only run on full/clean builds by default. Explicit runOnIncremental=true is required to execute mapped plugin execution during incremental workspace build. Existing projects and maven plugins that correctly use old default baviour will need to be updated... which is not nice, but I think this is justified by improved overall m2e stability. We should have made this change in 1.0.100... Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
Diffstat (limited to 'org.eclipse.m2e.lifecyclemapping.defaults')
-rw-r--r--org.eclipse.m2e.lifecyclemapping.defaults/lifecycle-mapping-metadata.xml4
1 files changed, 3 insertions, 1 deletions
diff --git a/org.eclipse.m2e.lifecyclemapping.defaults/lifecycle-mapping-metadata.xml b/org.eclipse.m2e.lifecyclemapping.defaults/lifecycle-mapping-metadata.xml
index 67ea13c1..c7c14d20 100644
--- a/org.eclipse.m2e.lifecyclemapping.defaults/lifecycle-mapping-metadata.xml
+++ b/org.eclipse.m2e.lifecyclemapping.defaults/lifecycle-mapping-metadata.xml
@@ -44,7 +44,9 @@
<versionRange>[2.4,)</versionRange>
</pluginExecutionFilter>
<action>
- <execute/>
+ <execute>
+ <runOnIncremental>true</runOnIncremental>
+ </execute>
</action>
</pluginExecution>
<pluginExecution>

Back to the top