[ 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 d
[ http://jira.codehaus.org/browse/MNG-514?page=comments#action_50605 ]
fabrizio giustina commented on MNG-514:
---
This is working as expected for me, direct provided dependencies are added but
transitive ones don't.
If nobody will comment on this I will
[ http://jira.codehaus.org/browse/MNG-514?page=comments#action_49652 ]
fabrizio giustina commented on MNG-514:
---
a quick sum up for requisites, the actual situation is really messy:
.classpath
- direct dependencies:
- include compile/test/provided
[ 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
[ http://jira.codehaus.org/browse/MNG-514?page=comments#action_43679 ]
kristian meier commented on MNG-514:
yesterday I run into this, without finding this bug before fixing it. so I
added a '*'-filter for the ScopeArtifactFilter, which allows to use
@
[ 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 sho
