[jira] Commented: (MNG-514) "Provided" dependencies not included in eclipse build path

["Kenney Westerhof (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MNG-514?page=comments#action_46367 ] 

Kenney Westerhof commented on MNG-514:
--------------------------------------

I made a testcase for eclipse, but since that doesn't use the full m2 environment that test always fails.
Here's how to reproduce:

- project A is the one you are calling eclipse:eclipse on
- it has a dependency on project B (in the local repo), packaging war (not sure if that matters).
- project B has a dependency on C (for instance) with scope=provided.

B ends up in .classpath, but C doesnt. Direct dependencies for A with scope=provided do end up in .classpath.

So it seems when transitively resolving deps the scope is lost (dependencyResolution = test).

> "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-plugins
>  Environment: Windows XP SP2, J2SE 5.0, running against main trunk in SVN.
>     Reporter: Nathaniel Stoddard
>     Assignee: Kenney Westerhof
>      Fix For: 2.0-beta-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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org