Skip to content

chore: untangling auth library parent and imported BOM#12737

Draft
suztomo wants to merge 1 commit intogoogleapis:mainfrom
suztomo:untangle-auth
Draft

chore: untangling auth library parent and imported BOM#12737
suztomo wants to merge 1 commit intogoogleapis:mainfrom
suztomo:untangle-auth

Conversation

@suztomo
Copy link
Copy Markdown
Member

@suztomo suztomo commented Apr 9, 2026

Maven Central does not allow uploading a set of artifacts having different group IDs.

  • The shared dependencies BOM (which uses gapic-generator-java-bom) should not import the auth BOM.
  • The google-auth-library-java/pom.xml should not use POM file of com.google.cloud.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request updates the project's parent POM configuration to use google-cloud-shared-config instead of the previous parent, updates various dependency versions, and refines the dependencyManagement section. Feedback was provided regarding the hardcoded version of mockito-core, the potential build failure for mockito-junit-jupiter due to the parent change, and the ambiguity of the <!-- Do not import --> comment in the POM file.

Comment on lines +144 to +148
<groupId>org.mockito</groupId>
<artifactId>mockito-core</artifactId>
<version>4.11.0</version>
<scope>test</scope>
</dependency>
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

high

The version for mockito-core is hardcoded here. It is recommended to use a property for consistency with other dependencies in this file. Additionally, the subsequent dependency mockito-junit-jupiter (starting at line 149) is missing a version; since the parent has changed from google-cloud-jar-parent to google-cloud-shared-config, it is likely no longer managed and will cause a build failure if a version is not explicitly provided.

</properties>

<dependencyManagement>
<!-- Do not import -->
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

The comment <!-- Do not import --> is ambiguous and potentially misleading, as it is immediately followed by several dependencies with <scope>import</scope>. If the intention is to discourage importing this root POM as a BOM, it should be clarified or moved to a more appropriate location. If it is a leftover from a previous iteration, it should be removed.

<project.findbugs.version>3.0.2</project.findbugs.version>
<deploy.autorelease>false</deploy.autorelease>
<project.error-prone.version>2.38.0</project.error-prone.version>
<project.error-prone.version>2.42.0</project.error-prone.version>
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Anything that requires this update?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Guava depends on this newer version and upper-bound check was failing.

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.

2 participants