You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Roman Kalukiewicz (JIRA)" <ji...@codehaus.org> on 2008/08/27 13:38:49 UTC
[jira] Commented: (MECLIPSE-15) "Provided" dependencies not
included in eclipse build path
[ http://jira.codehaus.org/browse/MECLIPSE-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=146161#action_146161 ]
Roman Kalukiewicz commented on MECLIPSE-15:
-------------------------------------------
It looks that now direct provided dependencies are resolved fine in {{.classpath}} and provided dependencies are not transitive, but provided dependencies of provided dependencies should be provided, that doesn't work.
If you consult
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope
then instead of having provided at intersection of provided/provided eclipse plugin behaves like there is '-'.
> "Provided" dependencies not included in eclipse build path
> ----------------------------------------------------------
>
> Key: MECLIPSE-15
> URL: http://jira.codehaus.org/browse/MECLIPSE-15
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Dependencies resolution and build path
> Environment: Windows XP SP2, J2SE 5.0, running against main trunk in SVN.
> Reporter: Nathaniel Stoddard
> Assignee: Kenney Westerhof
>
> When an eclipse project is generated for a project with a dependency whose scope is "provided", the dependency is not included in the build path of the project.
--
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