I recently moved my Maven-repository to a different location
(D:\m2repository, from the former C:\Users\\.m2\repository).
Of course I changed that in my settings (both in the
C:\Users\\.m2\settings.xml file as well as in Eclipse's Maven
settings) and Updated the Maven projects multiple times, but
'Project and External Dependencies' is a classpath container provided by
Buildship, for Gradle projects. No Maven projects should have it. i.e.
there should be no org.eclipse.buildship.core.gradleclasspathcontainer
classpath entry. Long story short, this is not m2e misbehaving.
Does your project ha
Ah - Gradle. Good to know.
I had originally imported these projects as Maven projects.
Then I had once experimented and tried to use Gradle for building them (i.e. I
added a “gradle nature” to them), but I then ran into an issue with some GWT
code that we are using (yes – blush – our project
