Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 2.7
-
Fix Version/s: None
-
Labels:None
-
Number of attachments :
Description
Every time I run eclipse:eclipse for one of my projects, the .classpath picks up some jms and jmx dependencies. However, they do not show up in dependency:tree or dependency:list.
I don't have a small test case, can you give me a way to diagnose?
spurious dependencies get included in projects I work on using maven-eclipse-plugin 2.5 through 2.8. Luckily, most of them aren't hateful.
However, recently a downstream project picked up servlet 3.0.1 and servlet-3.0.1 gets deployed EVEN THOUGH (as you note) it does not show up when using mvn dependency:* servlet 3.0 has been excluded in my pom, but it still gets in eclipse's .classpath.
2.9 doesn't seem to do this, but 2.9 can't create a working tomcat 7 deployment that works inside eclipse. I will be stuck using 2.5.1 FOREVER!