-
Notifications
You must be signed in to change notification settings - Fork 269
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
ProtobufExtract task not UP-TO-DATE when it should be #667
Comments
Hi. Could you please write your |
Sorry for ambiguity, I'm building the androidx project itself. To repro, you can do the following:
The build scan from step 3 will show that the task was not UP-TO-DATE because of the empty directory. |
This is much better. Is this reproducible on the |
yes |
@scott-pollock great, thanks. Will investigate on this weekend. |
Thanks! |
A bug in the protobuf-gradle-plugin is causing :datastore:datastore-preferences-proto:extractIncludeTestProto to be not UP-TO-DATE when it should be. See google/protobuf-gradle-plugin#667 Bug: NA Test: existing Change-Id: If2d89dc9e38bb879338f01b79909ea764bb391ce
This is the expected behavior at the moment. Bad behavior, but true. Will be fixed in the future, somewhere in version
|
This is a follow-up to If2d89dc9e38bb879338f01b79909ea764bb391ce. A bug in the protobuf-gradle-plugin is causing the extractIncludeTestProto tasks to be not UP-TO-DATE when they should be. See google/protobuf-gradle-plugin#667 Bug: NA Test: existing Change-Id: I77dfe1a5b716a573120c7fe7253bb1375a5a60cd
Any updates on the fixes? |
Are we still planning to fix this? |
ProtobufExtract task is not UP-TO-DATE when irrelevant input directories are added or removed.
See example below from AndroidX build:
This is surprising because
ProtobufExtract.getInputProtoFiles()
should only contain proto files.protobuf-gradle-plugin version: 0.9.0
The text was updated successfully, but these errors were encountered: