Barrie Treloar wrote:
I cant remember if this is already raised somewhere else, but there is similar problem with the scope "test". test means both testCompile and testRuntime (which themselves dont exist) so things like dependency:analyze reports errors because that level of granularity does not exist.
Reminds me of MDEP-152 and MDEP-146. Anyway, please let us keep this discussion focused on the original topic, otherwise I fear we won't get anywhere.
My concern was to allow plugins to easily/efficiently enforce resolution of certain dependencies with the scopes that we have in place. Extending the scope system to distinguish between test-compile and test-runtime is another story.
Benjamin --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
