Am 07/02/16 um 16:59 schrieb Robert Scholte: > > I agree that this should have been commons-io:2.4, but it matches the > documentation (g:a is unique and nearest wins). I expect that the problem > lies in the way Aether is used. > I assume that first the complete dependency graph is collected no matter > the scope. Next it is resolved so each dependency has the proper scope and > version. And finally there's the scope based filtering. > This order I would like to see it to start with scope filtering. This will > probably be more efficient too, since test-scoped dependencies are > filtered out from the beginning. >
Turned out I have been running maven-resources-plugin-3.0.1 but debugged maven-resources-plugin-3.0.2-SNAPSHOT. It's a bit different. The compile classpath does not contain any commons-io. It should contain commons-io-2.4. So that test dependency gets filtered out from the compile classpath. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
