Test is basically:
productFlavors {
javac {
useJack false
}
jack {
useJack true
}
}
$ ./gradlew :assembleJavacDebug :assembleJackDebug
$ ls -l build/outputs/apk/ | grep -v unaligned
total 443000
-rw-r--r--+ 1 jhansche staff 30074468 Feb 3 16:31 App-javac-debug.apk
-rw-r--r--+ 1 jhansche staff 21634256 Feb 3 16:32 App-jack-debug.apk
Notice the size difference is almost 10 MB. Checking the contents of the
compiled APKs shows that javac contains 3 (multidex) dex files:
$ unzip -l build/outputs/apk/App-javac-debug.apk | grep dex
8870148 02-03-16 16:31 classes.dex
9338456 02-03-16 16:31 classes2.dex
1275928 02-03-16 16:31 classes3.dex
while the Jack version contains 0 dex files:
$ unzip -l build/outputs/apk/App-jack-debug.apk | grep dex
$ unzip -l build/outputs/apk/App-jack-debug.apk | grep -c dex
0
Running `find build -name '*.dex'` also shows only the dex files that go
into the "Javac" flavor -- no files attributed to the "Jack" flavor.
On Wednesday, February 3, 2016 at 4:35:15 PM UTC-5, Joe Hansche wrote:
>
> Using 2.0 preview 9 and gradle plugin 2.0.0-alpha9, building with useJack
> true, I'm still seeing no classes.dex added in the APK. Was this a
> regression?
--
You received this message because you are subscribed to the Google Groups
"adt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
