davsclaus opened a new pull request, #30442:
URL: https://github.com/apache/camel/pull/30442

   # Description
   
   No Camel Maven plugin sets `requiredMavenVersion`, so `maven-plugin-plugin` 
derives it from the `maven-plugin-api` version, which is the `maven-version` 
property. That means every bump of `maven-version` has raised the Maven version 
that users need in order to run `camel-maven-plugin`, 
`camel-report-maven-plugin`, `camel-yaml-dsl-validator-maven-plugin` and the 
other plugins:
   
   | Plugins | `maven-version` | `requiredMavenVersion` in plugin.xml |
   |---|---|---|
   | 4.18.x | 3.9.12 | 3.9.12 |
   | 4.22.x | 3.9.16 | 3.9.16 |
   | main with #27192 (maven-version 3.9.16 → 3.10.0) | 3.10.0 | 3.10.0 |
   
   On Maven 3.9.x, a user would get "requires Maven version 3.10.0" from all 
the Camel plugins as soon as #27192 is merged.
   
   This PR:
   
   - sets `requiredMavenVersion` to **3.9.12** (released 2025-12) in the shared 
`maven-plugin-plugin` configuration in `parent/pom.xml`, so it no longer 
follows `maven-version`
   - raises the Maven version that the build enforces (root `pom.xml`) from 
3.9.6 (released 2023-11) to the same 3.9.12; AGENTS.md already says Maven 
3.9.12+
   - changes the getting-started guide from Maven 3.9.6 to 3.9.12
   
   For the 4.22 plugins this lowers the minimum from 3.9.16 to 3.9.12, and for 
the 4.18 plugins it stays the same.
   
   # Verification
   
   - Built `camel-maven-plugin`, `camel-report-maven-plugin` and 
`camel-yaml-dsl-validator-maven-plugin` with `-Dmaven-version=3.10.0` 
(`maven-core` and `maven-plugin-api` resolve to 3.10.0). All three build and 
their `plugin.xml` declares 
`<requiredMavenVersion>3.9.12</requiredMavenVersion>`. Without the pin they 
declare 3.9.16 today.
   - The root enforcer passes with Maven 3.10.1.
   
   After this is merged, #27192 can be rebased and merged.
   
   _Claude Code on behalf of davsclaus_
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to