Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-users] Where does m2e hide references to the Maven-archive?

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 still uses GWT - blush). I couldn’t figure out how to replace the Maven-plugin used for GWT for Gradle and then I gave up – at least for the time being.

I had then removed the gradle nature again from the projects but it seems to me that apparently something was still left behind, then.


For now I seem to have fixed the issue by manually removing 'Project and External Dependencies' from all builds paths – at least I get no more errors during builds right now.



From: m2e-users-bounces@xxxxxxxxxxx <m2e-users-bounces@xxxxxxxxxxx> On Behalf Of Fred Bricon
Sent: Dienstag, 19. November 2019 16:00
To: Maven Integration for Eclipse users mailing list <m2e-users@xxxxxxxxxxx>
Subject: Re: [m2e-users] Where does m2e hide references to the Maven-archive?


'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 have a build.gradle file? how did you import it in Eclipse?


On Tue, Nov 19, 2019 at 3:53 PM <michael.moser@xxxxxxxxxx> wrote:

I recently moved my Maven-repository to a different location (D:\m2repository, from the former C:\Users\<user>\.m2\repository).

Of course I changed that in my settings (both in the C:\Users\<user>\.m2\settings.xml file as well as in Eclipse’s Maven settings) and Updated the Maven projects multiple times, but for some stupid reason Eclipse builds still displays error messages like:


The container 'Project and External Dependencies' references non existing library 'C:\Users\<user>\.m2\repository\net\sf\dozer\dozer\5.5.1\dozer-5.5.1.jar'.


In the Projects Explorer under the virtual 'Project and External Dependencies' folder there is no library pointing to the old location listed.

If I go to the project’s properties -> Java Build Path -> libraries paths and expand the virtual 'Project and External Dependencies' folder, however, there are indeed tons of .jar file entries listed still pointing to the old path. Where are these coming from? I have searched my entire workspace for files containing the path ’C:\Users\<user>\.m2\repository’ and substrings there-of (down to ’repository’) and found nothing.

I have the suspicion that these are saved under “org.eclipse.buildship.core.gradleclasspathcontainer” but where does THAT come from? The is no such entry under the (E)Gradle-Preferences. And this also is a Maven-project, no Gradle anywhere. Where do these paths from the past possibly hide in Eclipse???


This is using v2019-03

BTW: when I build the project with Maven from the command line everything works dandy!


m2e-users mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit



"Have you tried turning it off and on again" - The IT Crowd

And if that fails, then

Back to the top