[ http://jira.codehaus.org/browse/MNG-514?page=comments#action_43503 ]
Kenney Westerhof commented on MNG-514:
--------------------------------------
A possible solution is to add the 'provided' jars to the test scope, because
the eclipse plugin
@requiresDependencyResolution test. But it should indeed include all scopes.
Another solution is to add a new scope 'all'.
Here's a possible patch: (no attachment because it's so small :))
Index:
maven-artifact/src/main/java/org/apache/maven/artifact/resolver/filter/ScopeArtifactFilter.java
===================================================================
---
maven-artifact/src/main/java/org/apache/maven/artifact/resolver/filter/ScopeArtifactFilter.java
(revision 225475)
+++
maven-artifact/src/main/java/org/apache/maven/artifact/resolver/filter/ScopeArtifactFilter.java
(working copy)
@@ -54,7 +54,7 @@
}
else if ( DefaultArtifact.SCOPE_TEST.equals( scope ) )
{
- providedScope = false;
+ providedScope = true;
compileScope = true;
runtimeScope = true;
testScope = true;
> "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
> Fix For: 2.0-beta-2
>
>
> 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]
