> I think the answer here is that nobody had a good example at the time!
And even when you do, you can use exclusions which you interesting mention in your next response ;-). So if you want a particular compile transitive dependency to be included only as test, exclude it and add it to your local pom as test. I agree that the local pom should have precise control over how the "scope" of a dependency gets defined. But Maven is all about convention over configuration. If the convention is that compile scope should override test scope, then that is what maven should do by default. In the rare cases when a user wishes to change this behaviour, maven should provide a way to configure a transitive dependency manually. This is very similar in concept to marking a transitve dependency as exclude. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
