Status Update
No update yet.
Comments
xa...@google.com
I am not sure I understand the use case. how can the benchmark be code to real world scenario when it's not possible to do right now ? which scenario is it ?
In any case, since this would be for benchmarking, this would clearly not be available through the public DSL. We should find a semi-private way of doing this (maybe the private variant API object could offer that functionality for instance or a property).
xa...@google.com
an...@google.com
We want benchmarks to measure code after Progaurd / R8, but it's not possible to turn that on for androidTests in library modules at the moment (to my knowledge?)
Benchmarks are also a public facing thing, but we have a plugin to help configure gradle builds for our users, so if support for this ends up in a private API, we could try to keep those usages localized to our code perhaps.
Description
Using latest Ladybug patch 1 on Mac OSX arm64, I checked out the Jetcaster project (https://github.com/android/compose-samples/tree/main ), and after syncing, I pressed Cmd-F9 to build the project.
It fails with the following error:
Note that this build error has no error location associated with it. From looking at the error panel tab (see screenshot) I can guess that it's related to the core/domain/ module. But it should be telling me more information -- which dependencies are bringing in the two versions. And ideally the error message should tell me more specifically how to avoid it. If the two files are identical (which I suspect they are, given that the path has the version number in it) I'm assuming this is just a matter of telling it to use one / skip one.
But the link we're pointing to in the error message, "https://developer.android.com/reference/tools/gradle-api/8.7/com/android/build/api/dsl/Packaging
for more information" isn't really helpful -- it's just the javadoc for the DSL API! I would have hoped for more dedicated information on how to resolve a conflict like this.