maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Mudrick (JIRA)" <j...@codehaus.org>
Subject [jira] Created: (MECLIPSE-677) Ordering "provided" java api dependencies entries above classpath container is wrong
Date Wed, 08 Dec 2010 16:33:58 GMT
Ordering "provided" java api dependencies entries above classpath container is wrong
------------------------------------------------------------------------------------

                 Key: MECLIPSE-677
                 URL: http://jira.codehaus.org/browse/MECLIPSE-677
             Project: Maven 2.x Eclipse Plugin
          Issue Type: Bug
          Components: Core : Dependencies resolution and build path (.classpath)
    Affects Versions: 2.6
            Reporter: Kevin Mudrick
         Attachments: meclipse-java-deps-path.diff

The change for MECLIPSE-437 causes all java.* and javax.* dependencies to come before the
classpath container(s).  However, I feel this should only apply to actual compile scoped dependencies.
 Those marked as "provided" should not come before the classpath container.

It appears as though others have run into this problem as well - [~skajotde] commented on
the original issue.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message