be aware that: 1. it's not because a plugin is on ...
# gradle
m
be aware that: 1. it's not because a plugin is on classpath that it is applied 2. multiple plugins can contribute the same configuration names 3. configurations can be created "dynamically" (aka, inspect other configurations, create a different one with a different name, say
compile
->
testCompile
... I'm not saying this is always the case, but that's a possibility.