[XABT] Add ArtifactFilename
metadata for @(AndroidMavenLibrary)
item.
#9479
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.
Fixes: #9465
In all of the examples we used when developing and testing
@(AndroidMavenLibrary)
the Maven artifact filename followed the pattern{artifact.Id}-{artifact.Version}.[jar|aar]
, so this is the default filename we construct for the user.However, there exists some packages like React that do not follow this pattern and instead do eg:
react-android-0.76.0-release.aar
. Attempting to use@(AndroidMavenLibrary)
for React produces the following error:To support these cases, add a new optional metadata
ArtifactFilename
that can be specified to override the Maven filename of the artifact.This allows our tasks to properly download the artifact and avoid the error.