Status Update
No update yet.
Comments
ma...@gmail.com
We use build flavours heavily with a lot of common code. The refactoring support in AS is really good but it continually catches us out when it doesn't work across all flavours in a project. It's a big gap for serious product development.
xa...@google.com
xa...@google.com
We at my company need this same feature. We have a lot of white labels and need refactor the same class across flavours. :(
im...@google.com
I need this feature too...
im...@google.com
+1 My company also need this feature.
Description
4.0-milestone-1-all.zip
Android Plugin Version:
3.0.0-alpha1
Module Compile Sdk Version:
android-O
Module Build Tools Version:
26.0.0-rc2
Android SDK Tools version:
26.0.2
Expected:
Proguard build works fine on this commit (before the 3.0.0alpha1 update)
fd08ec39553006cb116d78a09c52bf93b41d357b
Actual
After Upgrading to 3.0.0-alpha1 it seems that gradle proguard (breaks) is not taken from Firebase libs properly (maybe an issue with aapt2 or unpacking the consumerProguardFiles?)
528800098595d66bdad61ec8e5caeaaa2f150a86
Reproduction steps:
Run:
./gradlew clean transformClassesAndResourcesWithProgardForPayGermanyBleedingRelease
I created a repo project that is used for various issues we come up with gradle during last 2 years, and it still proves quite useful, I would strongly suggest using something like this when testing gradle build tools.