jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
Signup
Maven 2.x Eclipse Plugin
  • Maven 2.x Eclipse Plugin
  • MECLIPSE-640

Spurious dependency?

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 2.7
  • Fix Version/s: None
  • Component/s: Core : Dependencies resolution and build path (.classpath)
  • Labels:
    None
  • Number of attachments :
    0

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?

Activity

  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Kow Unk added a comment - 30/Mar/12 1:57 PM - edited

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!

Show
Kow Unk added a comment - 30/Mar/12 1:57 PM - edited 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!

People

  • Assignee:
    Unassigned
    Reporter:
    Benson Margulies
Vote (0)
Watch (0)

Dates

  • Created:
    15/Feb/10 9:47 AM
    Updated:
    30/Mar/12 2:00 PM
  • Atlassian JIRA (v5.2.7#850-sha1:b2af0c8)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.