[ http://jira.codehaus.org/browse/MNG-514?page=comments#action_50617 ]
Kenney Westerhof commented on MNG-514:
--------------------------------------
There was a discussion on the dev list a month ago or more about this. I'm not
sure
what the outcome was, but I believe that scope=provided dependencies should be
transitive; they
indicate that the target environment MUST provide those artifacts. Since
eclipse is not the
target environment, and it _needs_ those artifacts because you'll get linkage
problems
('class ... referenced from .class but not found' errors), I think provided
should be
transitive as well. Let the final project decide.
Btw, I didn't know what the .wtpmodules was for, but if it is for .war's, I
agree on the different
handling.
> "Provided" dependencies not included in eclipse build path
> ----------------------------------------------------------
>
> Key: MNG-514
> URL: http://jira.codehaus.org/browse/MNG-514
> Project: Maven 2
> Type: Bug
> Components: maven-eclipse-plugin
> Environment: Windows XP SP2, J2SE 5.0, running against main trunk in SVN.
> Reporter: Nathaniel Stoddard
> Assignee: Kenney Westerhof
> Fix For: 2.0.1
>
>
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
