> What's wrong here? My project A only uses L for unit tests so I define the > dependency with > 'test' scope. But, at the end, I want L to be on my classpath since project A > depends on > project B for production, and B needs (transitively) library L also for > production. (By production,
OK so in a nutshell... A compile-dep B A test-dep L B compile-dep L Because A has a test-dep to L, that overrides the B compile-dep on L which is brought in to A transitively. You are effectively downgrading the scope of this library by declaring it locally as a test dependency. What kind of package are you building? Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
