Forces Eclipse to build once per second

[orlade]

I can't figure out if this is as designed or not, but with the plugin listed in pom.xml, Eclipse invokes "Maven Project Builder" once every second, seemingly only to update the timestamp in the git.properties file. I tried adding a phase tag to the plugin, but it didn't help. Here's what I'm using:

  <!-- Git build helper -->
  <plugin>
    <groupId>pl.project13.maven</groupId>
    <artifactId>git-commit-id-plugin</artifactId>
    <version>2.1.9</version>
    <executions>
      <execution>
        <phase>package</phase>
        <goals>
          <goal>revision</goal>
        </goals>
      </execution>
    </executions>

    <configuration>
      <dotGitDirectory>${project.basedir}/../.git</dotGitDirectory>
      <generateGitPropertiesFile>true</generateGitPropertiesFile>
      <generateGitPropertiesFilename>src/main/resources/git.properties</generateGitPropertiesFilename>
      <failOnNoGitDirectory>true</failOnNoGitDirectory>
    </configuration>
  </plugin>

[ktoso]

This is definitely not "as designed", but rather than the plugin I think that's somethign weird with eclipse... I'm not an eclipse user - can you reproduce this on different eclipse versions?

[ktoso]

I'll close due to inactivity if no more details are provided, what versions of stuff are you using?

[orlade]

I'm using Eclipse Kepler Service Release 1, Build id: 20130919-0819, and m2e 1.4.0. I can't really try out other versions at the moment, so close it if you like.

[Loki-Afro]

Same Issue here.
Version: Kepler Service Release 2
Build id: 20140224-0627

The solution is some kind of lifecycle mapping in the eclipse configuration or directly into the pom.
I guess spring-boot uses this plugin too and they came up with the lifecycle mapping solution...

[lordkada]

I've the same problem. My Eclipse is:
Version: Luna Release (4.4.0)
Build id: 20140612-0600

[TheSnoozer]

Hi,
the issue #151 seems to be related to this problem.
The issue #151 was resolved with the PR #152

The fix should be included in version 2.1.13.
Can someone do me the favour and check if the problem is still present (I currently can not reproduce it)?

Thanks,

[nealeu]

I just noticed this and related issues, as we are using this plugin but not having them.

The reason this is happening is that the src/ folder is a watched folder in Eclipse for files that are edited by humans. The target folder is where all derived resources should go.

Our settings specify:

<phase>prepare-package</phase>

and

<generateGitPropertiesFilename>target/classes/properties/git.properties</generateGitPropertiesFilename>

Later phases then package this for deployment

[TheSnoozer]

@nealeu,
this makes sense.....I just found two articles ([1] and [2]) that support the thesis that eclipse or the "Maven Project Builder" will be invoked when it detects some changes in the project.

quote from [2]

Plug-ins contribute incremental project builders to the platform in order to implement specialized resource transformations. For example, the Java development tools (JDT)define an incremental project builder that compiles a Java source file into a class file any time a file is added or modified in a Java project.

I'm not sure though if the "Maven Project Builder" is an incremental project builder, but anyhow it sounds like this is by design. Maybe the only thing we could do here is put a warning in the readme...

Thanks for your input and feedback here @nealeu !

[1] https://www.eclipse.org/articles/Article-Builders/builders.html
[2] http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fguide%2FresAdv_builders.htm

[TheSnoozer]

I added a note to the readme and based on the discussion I would go ahead and close this issue since there is not much we can do to change the behaviour of internal IDE project builder.