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>

1 files changed, 1 insertions, 1 deletions

diff --git a/org.eclipse.m2e.core/src/org/eclipse/m2e/core/internal/lifecyclemapping/LifecycleMappingFactory.java b/org.eclipse.m2e.core/src/org/eclipse/m2e/core/internal/lifecyclemapping/LifecycleMappingFactory.java
index f3c405fa..c4c78dde 100644
--- a/org.eclipse.m2e.core/src/org/eclipse/m2e/core/internal/lifecyclemapping/LifecycleMappingFactory.java
+++ b/org.eclipse.m2e.core/src/org/eclipse/m2e/core/internal/lifecyclemapping/LifecycleMappingFactory.java
@@ -837,7 +837,7 @@ public class LifecycleMappingFactory {
 
   public static MojoExecutionBuildParticipant createMojoExecutionBuildParicipant(IMavenProjectFacade projectFacade,
       MojoExecution mojoExecution, IPluginExecutionMetadata executionMetadata) {
-    boolean runOnIncremental = true;
+    boolean runOnIncremental = false;
     boolean runOnConfiguration = false;
     Xpp3Dom child = ((PluginExecutionMetadata) executionMetadata).getConfiguration().getChild(
         ELEMENT_RUN_ON_INCREMENTAL);