Add deps + scope test. #33
Conversation
|
What I'm understanding from this test case: Ales would like to "filter" out dependencies by scopes, but in the example shown, jboss-logging is not resolved as a dependency from XNIO because the XNIO POM puts it in "provided" scope. Therefore there's nothing to filter out, and the test fails. Is that a correct summation? My branch has a modified version of this test which eliminates the reliance on system properties and uses the standard settings.xml we package with the SWR tests. If this description above is correct, please let me know so I can open an appropriate JIRA. Sorry it took a bit to decode what you're looking for here. |
|
Reference: XNIO POM in question which Ales would like to pull in jboss-logging: http://search.maven.org/remotecontent?filepath=org/jboss/xnio/xnio-api/3.1.0.Beta7/xnio-api-3.1.0.Beta7.pom |
|
Well, we coould actually say un-filter then. :-) |
|
I think this is a valid use case. If we say strategy, we do not distinguish filtering and un-filtering. Strategy should allow you to say what you want, whereas filter will reduce results that Maven resolves by default. There is no "maven resolved by default" for strategies. |
|
Agreed. So wondering aloud as I play with the impl how we get Aether to |
|
Found the magic sauce in Aether, and added some API love to give us hooks. Upstream: ALRubinger@af3a87e and ALRubinger@6e125ce. |
No description provided.