Skip to content

Specify a version for maven-deploy-plugin, even though we don't use that plugin.#8163

Merged
copybara-service[bot] merged 1 commit intomasterfrom
test_854706425
Jan 12, 2026
Merged

Specify a version for maven-deploy-plugin, even though we don't use that plugin.#8163
copybara-service[bot] merged 1 commit intomasterfrom
test_854706425

Conversation

@copybara-service
Copy link
Contributor

Specify a version for maven-deploy-plugin, even though we don't use that plugin.

This prevents Maven from printing a warning (to standard output?), which interferes with our attempt to print out the current version as part of generating JDiff.

RELNOTES=n/a

… that plugin.

This prevents Maven from printing a warning (to standard output?), which interferes with our attempt to [print out the current version](https://github.com/google/guava/blob/606646223f61157fd9af3a02646c97c4296ac21e/_util/util.sh#L25) as part of generating JDiff.

RELNOTES=n/a
PiperOrigin-RevId: 855265235
@copybara-service copybara-service bot merged commit e99dd31 into master Jan 12, 2026
@copybara-service copybara-service bot deleted the test_854706425 branch January 12, 2026 17:42
copybara-service bot pushed a commit to google/jimfs that referenced this pull request Jan 13, 2026
… that plugin.

Compare cl/855265235 / google/guava#8163.

As with Guava, this should fix [a JDiff breakage](https://github.com/google/jimfs/actions/runs/20968696648/job/60266138089#step:5:491) that is preventing us from deploying snapshot docs. (I'd forgotten that we run JDiff for jimfs!)

I would guess that some of our other projects are likewise seeing warnings for the lack of a `maven-deploy-plugin` version, and it might be nice to fix them. But I didn't find any examples in the couple projects I looked at, in part because those projects don't have a JDiff step to fail as a result.

(The irony is that we have this problem only because we tried to get the version number from Maven in the Correct way instead of parsing XML with regular expressions :))

RELNOTES=n/a
PiperOrigin-RevId: 855804267
copybara-service bot pushed a commit to google/jimfs that referenced this pull request Jan 13, 2026
… that plugin.

Compare cl/855265235 / google/guava#8163.

As with Guava, this should fix [a JDiff breakage](https://github.com/google/jimfs/actions/runs/20968696648/job/60266138089#step:5:491) that is preventing us from deploying snapshot docs. (I'd forgotten that we run JDiff for jimfs!)

I would guess that some of our other projects are likewise seeing warnings for the lack of a `maven-deploy-plugin` version, and it might be nice to fix them. But I didn't find any examples in the couple projects I looked at, in part because those projects don't have a JDiff step to fail as a result.

(The irony is that we have this problem only because we tried to get the version number from Maven in the Correct way instead of parsing XML with regular expressions :))

RELNOTES=n/a
PiperOrigin-RevId: 855836740
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.

1 participant