Skip to content

Verify the build against Maven 4 as well - #330

Open
slachiewicz wants to merge 1 commit into
apache:masterfrom
slachiewicz:ci-verify-maven4
Open

Verify the build against Maven 4 as well#330
slachiewicz wants to merge 1 commit into
apache:masterfrom
slachiewicz:ci-verify-maven4

Conversation

@slachiewicz

Copy link
Copy Markdown
Member

Adds maven4-enabled: true, which appends 4.0.0-rc-6 to the existing Maven 3 matrix rather than replacing it — so the plugin keeps being built and tested with Maven 3 and additionally gets verified against Maven 4. The shared workflow also excludes the {jdk: 8, maven: 4.x} cell automatically, since Maven 4 needs JDK 17+.

Part of establishing which Maven 3 plugins already build clean on Maven 4 ahead of the 4.0.0 GA. Same change as apache/maven-javadoc-plugin#1350. Context in apache/maven#12676.

If the Maven 4 cell turns out to fail, that is the useful result — better to know now than at GA.

Adds maven4-enabled, which appends the Maven 4 version to the existing
Maven 3 matrix rather than replacing it, so the plugin keeps being built
and tested with Maven 3 and additionally gets checked against 4.0.0-rc-6.

Part of finding out which Maven 3 plugins already build clean on Maven 4
ahead of the 4.0.0 GA.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant