Skip to content

Conversation

@raych1
Copy link
Member

@raych1 raych1 commented Nov 21, 2025

Fixed #12506

Copilot AI review requested due to automatic review settings November 21, 2025 23:19
@raych1 raych1 requested a review from a team as a code owner November 21, 2025 23:19
Copilot finished reviewing on behalf of raych1 November 21, 2025 23:22
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds support for including the Java groupId when constructing package names for API view creation, addressing issue #12506. The implementation ensures that Java packages are properly identified with their full Maven coordinates (groupId:artifactId format).

  • Adds logic to construct full package name with groupId prefix for Java libraries
  • Includes helpful documentation comments showing PackageInfoFiles parameter format

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File Description
eng/common/scripts/Detect-Api-Changes.ps1 Adds groupId prefix to package artifact name when Group property is available, following the Maven coordinate pattern used in Validate-All-Packages.ps1
eng/common/pipelines/templates/steps/validate-all-packages.yml Adds documentation comment showing example format for PackageInfoFiles parameter
eng/common/pipelines/templates/steps/create-apireview.yml Adds documentation comment showing example format for PackageInfoFiles parameter

@raych1 raych1 closed this Nov 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update APIReview scripts to use full name for Java libraries

2 participants