Mostly reverted ${maven.build.timestamp} changes from 875ea242

${maven.build.timestamp} interpollation causes unexpected
"stale project configuration" error markers. reverted to the old
behaviour when m2e left ${maven.build.timestamp} uninitialized.

Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>

1 files changed, 3 insertions, 2 deletions

diff --git a/org.eclipse.m2e.core/src/org/eclipse/m2e/core/internal/embedder/MavenImpl.java b/org.eclipse.m2e.core/src/org/eclipse/m2e/core/internal/embedder/MavenImpl.java
index 608f9ee3..5d35bdb0 100644
--- a/org.eclipse.m2e.core/src/org/eclipse/m2e/core/internal/embedder/MavenImpl.java
+++ b/org.eclipse.m2e.core/src/org/eclipse/m2e/core/internal/embedder/MavenImpl.java
@@ -23,7 +23,6 @@ import java.io.OutputStream;
 import java.util.ArrayList;
 import java.util.Arrays;
 import java.util.Collections;
-import java.util.Date;
 import java.util.HashSet;
 import java.util.List;
 import java.util.Properties;
@@ -188,7 +187,9 @@ public class MavenImpl implements IMaven, IMavenConfigurationChangeListener {
   public MavenExecutionRequest createExecutionRequest(IProgressMonitor monitor) throws CoreException {
     MavenExecutionRequest request = new DefaultMavenExecutionRequest();
 
-    request.setStartTime( new Date() );
+    // this causes problems with unexpected "stale project configuration" error markers
+    // need to think how to manage ${maven.build.timestamp} properly inside workspace
+    //request.setStartTime( new Date() );
 
     if(mavenConfiguration.getGlobalSettingsFile() != null) {
       request.setGlobalSettingsFile(new File(mavenConfiguration.getGlobalSettingsFile()));