Register gradle outputs of ksp, and inputs of packaging tasks #32
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Solves: random Gradle error in consumer projects:
and
I believe Gradle was not aware of the zodable task outputs, and was therefore in some kind of race condition in which it would often error out (but work most of the time). There were also cases in which
the outputs of the KSP plugin were not declared (and not mapped to the inputs of creating the zodable packages), so there was another race there. This would sometimes result in
FileNotFoundExceptionon outputs of KSP e.g.dependencies.txt, though I only saw this problem after fixing the first problem.This change allows Gradle to consistently work without error for both inputs and outputs.