Skip to content

Verify the plugin still compiles against its declared prerequisite #1683

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
slachiewicz wants to merge 1 commit into from
+23 −0
Closed

Verify the plugin still compiles against its declared prerequisite #1683

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 23 additions & 0 deletions .github/workflows/maven-verify.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,3 +27,26 @@ jobs:
uses: apache/maven-gh-actions-shared/.github/workflows/maven-verify.yml@v5
with:
maven4-enabled: true

# The verify matrix runs current Maven only, so nothing checks the plugin against the
# version <prerequisites> claims to support. Compiling main and test sources against that
# baseline catches API drift without paying for a full test run.
baseline:
name: Baseline (Maven 3.6.3 API)
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1

- name: Set up JDK
uses: actions/setup-java@b6effb05e454b25005698d916606bdc6ffcbf961 # v5.7.0
with:
java-version: '21'
distribution: 'zulu'
cache: 'maven'

# Keep in step with <prerequisites><maven> in the POM. `clean` matters: without it a
# populated target/ would let the compiler skip, and the job would pass without having
# compiled anything against the baseline.
- name: Compile against the declared prerequisite
run: mvn -B --no-transfer-progress -DmavenVersion=3.6.3 clean test-compile
Loading