Support ClientCore libraries in Find-java-Artifacts-For-Apireview #43452
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.
Description
Adds an additional search for
sources.jar
files in theio.clientcore*
groupId in theFind-java-Artifacts-For-Apireview
. At this time there should be no mixing and matching ofcom.azure
andio.clientcore
packages in the same release group. Unfortunately, that PowerShell function only accepts the artifact directory and package name when performing the search and in the release pipeline case the artifact directory is the root build directory for the DevOps pipeline. So, there isn't a way to determine whether the package is in thecom.azure
orio.clientcore
groupId, meaning this isn't the ideal solutions but should work in the interim whileio.clientcore
packages aren't common.All SDK Contribution checklist:
General Guidelines and Best Practices
Testing Guidelines