IssueTracker

DESCRIBE THE ISSUE IN DETAIL:

We are trying to write a gradle plugin that supports Android. We'd like to create one gradle dependency configuration per sourceset, and then have a resolvable configuration (and gradle tasks) per variant. To do this, we need to know which android sourceSets are used by each variant.

In the old AGP APIs, we could use variant.sourceSets, and then use the sourceSet names to find the corresponding dependency configurations.

In the new AGP APIs, the source set names are not exposed from variants, so it's hard to determine which configurations should used by each variant. We have to hardcode some naming convention and determine the 'hierarchy' of configurations ourselves.

For example, our gradle plugin might define dependency configurations like pluginDeps (the 'main' sourceset), debugPluginDeps, androidTestPluginDeps, androidTestDebugPluginDeps, ... for our users. Then, we would define tasks per variant / testVariant, so for debug we might have:

• myDebugTask which uses dependencies from pluginDeps and debugPluginDeps (of course, not directly but through a resolvable configuration)
• myAndroidTestDebugTask which uses all of pluginDeps, debugPluginDeps, androidTestPluginDeps, androidTestDebugPluginDeps, etc.

We'd rather be able to use the existing logic in AGP, than have to hardcode all those rules of how configurations are named and used by variants.