Maven not adding jars to classpath

Question

I'm using eclipse indigo and maven 3.1

When I add a new dependency in pom.xml and run maven clean by right-clicking on pom.xml, maven is downloading missing jars to my local repository but not adding them to my list of referenced libraries.

After many hours of struggling I found out that I can solve this by running

mvn eclipse:eclipse -Dwtpversion=2.0

from command line each time after adding a new dependency. When I run maven clean from eclipse after doing this then the jars are added to referenced libraries.

Anybody know why this is happening like this?

because maven has no control over eclipse build path

Saddam Abu Ghaida
– Saddam Abu Ghaida

2013-09-26 08:38:12 +00:00
Commented Sep 26, 2013 at 8:38 — Saddam Abu Ghaida
– Saddam Abu Ghaida, Commented Sep 26, 2013 at 8:38

Community · Accepted Answer · 2017-05-23 11:50:50Z

5

Be carefull not to mix up the maven-eclipse-plugin and the m2e Maven eclipse integration.

You should use the Maven eclipse integration (m2). If you have maven commands in your IDE I suppose that you have installed m2e successfully (if not check this answer). In this case you can convert the project to a Maven project and the Maven Dependencies will be added as a Library to your Build Path.

As far as I know, if you use eclipse:eclipse the maven-eclipse-plugin will "mess up" your eclipse .classpath file and put every dependency as an own entry to the buildpath (and possibly the m2e configuration will be overwritten).

So both "tools" have different concepts that must not be used together. You have to take a decision which integration you prefer - IMHO m2e is mostly used.

edited May 23, 2017 at 11:50

CommunityBot

11 silver badge

answered Sep 27, 2013 at 9:37

FrVaBe

49.6k19 gold badges131 silver badges166 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Robert Scholte Over a year ago

eclipse:eclipse can be described as a push-mechanism. With every change to the pom.xml you might need to close Eclipse, run the goal and start Eclipse again. Whereas the m2eclipse uses pulling. It 'listens' to every change of the pom.xml and can change the eclipse environment immediately (of force it with Update project from the context menu)

Collectives™ on Stack Overflow

Maven not adding jars to classpath

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related