[m2e-users] Does change in classpath trigger "Project configuration out-

[Simon Niederberger <simon.niederberger@xxxxxxx>]

I’m working on a fairly large multi-module project. In a typical workspace, about half the submodule projects are closed in Eclipse, and m2e works of the SNAPSHOT artefacts. Very often (but not always), a pull from the GIT repo results in several projects reporting an «out-of-date» project configuration (which is easily resolved with a Maven update). The only thing changing during the pull is that some SNAPSHOTs have changed, and thus the classpath. I don’t find any other noteworthy entry in the m2e logfile (org.eclipse.m2e.logback.configuration/0.log with level DEBUG)

In this issue, https://bugs.eclipse.org/bugs/show_bug.cgi?id=471718, Igor describes marking the project configuration out-of-date only as a consequence of a change in lifecycle mapping.

I’d like to understand why m2e marks the project configuration as «out-of-date» even though – imho – the lifecycle mapping has not changed at all. Any pointers?


Simon