[jira] (MECLIPSE-640) Spurious dependency?

["Kow Unk (JIRA)" <ji...@codehaus.org>]

    [ https://jira.codehaus.org/browse/MECLIPSE-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=295458#comment-295458 ] 

Kow Unk commented on MECLIPSE-640:
----------------------------------

*spurious* dependencies get included in projects I work on from 2.5 through 2.8.  Luckily, some 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:*

2.9 doesn't seem to do this, but 2.9 can't create a working tomcat 7 deployment that works inside eclipse.    
                
> Spurious dependency?
> --------------------
>
>                 Key: MECLIPSE-640
>                 URL: https://jira.codehaus.org/browse/MECLIPSE-640
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Bug
>          Components: Core : Dependencies resolution and build path (.classpath)
>    Affects Versions: 2.7
>            Reporter: Benson Margulies
>
> 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?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira