[Xamarin.Android.Tools.Bytecode-Tests] Fix BuildClasses #1013
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.
The
BuildClasses
target runs on every rebuild:The cause for the warnings -- and the repetitive
BuildClasses
targetexecution -- is that the
@(_BuildClassOutputs)
item group is wrong;from the Dignostic build log:
obj/Debug-net7.0/classes/Collection.class
doesn't exist because itwill never exist; the file created is actually
obj/Debug-net7.0/classes/java/util/Collection.class
.Note the "missing"
java/util
in the path.The cause of the missing
java/util
is that@(_BuildClassOutputs)
uses
%(RecursiveDir)
, which only expands**
wildcards, whileCollection.java
comes from:Note the lack of
**
. Consequently,%(RecursiveDir)
expanded asthe empty string, which is why
java/util
was "lost".Fix this by introducing wildcards:
This fixes the repetitive
BuildClasses
execution: