Skip to content

build(deps): pin unpinned Maven plugins for Airlock - #14962

Open
hj690 wants to merge 2 commits into
googleapis:mainfrom
hj690:fix-airlock-unpinned-maven-plugins
Open

hj690 wants to merge 2 commits into
googleapis:mainfrom
hj690:fix-airlock-unpinned-maven-plugins

Conversation

@hj690

@hj690 hj690 commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Pin unpinned Maven build plugins across the monorepo to versions available in Airlock (b/568717591).

  • Without explicit plugin versions, Maven queries maven-metadata.xml and resolves newly published Central releases during the Airlock audit.
  • Pin flatten-maven-plugin (1.8.0), exec-maven-plugin (3.5.0), and fmt-maven-plugin (2.25) in standalone and root module POMs.
  • Add maven-checkstyle-plugin (3.6.0) and maven-resources-plugin (3.3.1) to google-cloud-shared-config <pluginManagement>. Pin maven-checkstyle-plugin in gax-bom, which uses a released parent.
  • Pin maven-assembly-plugin (3.7.1) in google-cloud-firestore and maven-shade-plugin (3.6.1) in storage-shared-benchmarking.

@hj690
hj690 requested review from a team as code owners November 10, 2026 17:14

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

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.

Code Review

This pull request explicitly defines missing plugin versions and group IDs across several Maven POM files, including flatten-maven-plugin, exec-maven-plugin, maven-checkstyle-plugin, maven-resources-plugin, and fmt-maven-plugin. These changes improve build reproducibility and stability. I have no additional feedback to provide.

@blakeli0

Copy link
Copy Markdown
Contributor

Do we have other unpinned Maven plugin versions? My AI reviews flags two possible cases:

  • maven-assembly-plugin in google-cloud-firestore/pom.xml only shows under Maven 3.10, which the ubuntu-22.04 runners already use. The warning is in this PR's own CI log.
  • maven-shade-plugin in storage-shared-benchmarking/pom.xml is in a profile-gated module, like the coverage-report one the PR does pin.

@@ -102,6 +102,7 @@
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-checkstyle-plugin</artifactId>
<version>3.6.0</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.

Not directly related to this PR, but if we change gax-bom to reference java-shared-config in this repo, instead of pin java-shared-config version, I think we can get the version automatically.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Yeah good point, I'll send a follow up PR for this!

<artifactId>maven-resources-plugin</artifactId>
<version>3.3.1</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.

I think this pom eventually inherit from java-shared-config, do we need the version here?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

You're right, thanks. I removed the inline pin in a376c5d. The effective version is still 3.3.1.

… pin

- Pin maven-assembly-plugin 3.7.1 in google-cloud-firestore. Maven 3.10
  warns about the missing version; Maven 3.9 resolves 3.7.1 today.
- Pin maven-shade-plugin 3.6.1 in the profile-gated
  storage-shared-benchmarking module.
- Remove the maven-resources-plugin pin from google-cloud-spanner-executor.
  The module inherits 3.3.1 from java-shared-config pluginManagement.
@hj690
hj690 requested review from a team as code owners November 11, 2026 15:20
@hj690

hj690 commented Nov 11, 2026

Copy link
Copy Markdown
Contributor Author

Do we have other unpinned Maven plugin versions? My AI reviews flags two possible cases:

Good catch, thanks! Both were real, and both are pinned in a376c5d.

@hj690 hj690 added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Nov 11, 2026
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Nov 11, 2026

This branch has not been deployed

No deployments
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.

3 participants