[
https://jira.codehaus.org/browse/MECLIPSE-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MECLIPSE-677.
-----------------------------------
Resolution: Won't Fix
Please refer to
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
if you're wondering why this issue was closed out.
> Ordering "provided" java api dependencies entries above classpath container
> is wrong
> ------------------------------------------------------------------------------------
>
> Key: MECLIPSE-677
> URL: https://jira.codehaus.org/browse/MECLIPSE-677
> Project: Maven 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 was sent by Atlassian JIRA
(v6.1.6#6162)
