Provide configurations for flavor+type combinations. [37034891]

Fixed

Feature Request

Status Update

No update yet.

Description

ja...@gmail.com

created issue #1

Mar 29, 2015 05:12AM

Source sets are created for the combinations as per

http://tools.android.com/tech-docs/new-build-system/user-guide#TOC-Sourcesets-and-Dependencies. Since the code in these source sets can have specific dependencies associated configurations should also be created.

In the linked example, I would expect to be able to add a dependency with flavor1DebugCompile, for example.

Comments

je...@google.com <je...@google.com> Mar 30, 2015 10:44PM

Assigned to je...@google.com.

xa...@android.com <xa...@android.com> #2Mar 31, 2015 05:47PM

can you share your android studio version

fl...@gmail.com <fl...@gmail.com> #3Apr 1, 2015 04:48PM

Is this happening with Studio 3.0?

[Deleted User] <[Deleted User]> #4Aug 24, 2015 04:04PM

Note: This worked for me on Windows 7 Pro 32-bit (with Android Studio 2.3.3). Seems like an issue with adt-branding module (which should contain the "/idea/AndroidStudioApplicationInfo.xml" resource).

ra...@gmail.com <ra...@gmail.com> #5Jul 21, 2016 12:21PM

Hi, also happened on Mac Book Pro 15 retina mi-2015
MacOs Sierra 10.12.6
Android Studio 2.3.3
java version "1.8.0_51"
Java(TM) SE Runtime Environment (build 1.8.0_51-b16)
Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)

[Deleted User] <[Deleted User]> #6Apr 26, 2017 08:47AM

Thank you for this feedback. Your feedback helps make sure Android development tools are great! Given your issues has been resolved I am closing this issue.

[Deleted User] <[Deleted User]> #7Apr 26, 2017 12:40PM

FYI - this process is going to change in Gradle plugin 2.5:

http://tools.android.com/tech-docs/new-build-system/2-5-alpha-gradle-plugin/trying-gradle-plugin-2-5

xa...@google.com <xa...@google.com> #8May 26, 2017 04:57PM

Marked as fixed, reassigned to xa...@google.com.

The configurations are created (like they were before). However instead of doing:

configurations {
flavor1DebugImplementation
}

dependencies {
flavor1DebugImplementation ...
}

You can now just put the dependencies block inside the afterEvaluate and not create the configurations manually. It's a bit better, but not perfect. We still have to wait until the variant combinations are computed to create the right configuration objects.

afterEvaluate {
dependencies {
flavor1DebugImplementation ...
}
}