-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
all_android_tools_deploy.jar
doesn't contain AutoValue's annotation processor
#24287
Comments
@fmeum FYI. |
Did this work with 7.3.0? Are you depending on |
Yes, we had no issue with 7.3.x. |
Here's a bit more detailed log
|
@bazel-io fork 7.4.1 |
A reproducer would be very helpful. What happens if you build |
Building DexFileSplitter didn't produce any issue... |
I'm wondering why |
It's a change that can break builds that used to pass, but I'm not yet sure that it's really Bazel's compared to just the dangers of unspecified deps. It can probably be fixed without a new Bazel release, but that requires confirmation from the Android team. |
Yes, we do use the annotation itself and the processor (these libs are listed in our maven dependencies). |
cc @ahumesky |
And building an android app with 7.4.1 also works for me and indeed builds the DexFileSplitter target in the course of the build:
Is DexFileSplitter being used in some other context? A minimal repro would be ideal. I know that Spotify maintains a fork of Bazel to implement missing features in the native Android rules, so I understand that might be tricky. |
Description of the bug:
The final all_android_tools_deploy.jar doesn't contain AutoValue's annotation processor class.
Which category does this issue belong to?
android tools
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
I wasn't able to reproduce it in a sample project, but we see it in our project.
Basically, the error says:
Which operating system are you running Bazel on?
macOS
What is the output of
bazel info release
?7.4.0
If
bazel info release
returnsdevelopment version
or(@non-git)
, tell us how you built Bazel.No response
What's the output of
git remote get-url origin; git rev-parse HEAD
?No response
If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.
It might be related to: #23709
Have you found anything relevant by searching the web?
No response
Any other information, logs, or outputs that you want to share?
No response
The text was updated successfully, but these errors were encountered: