davsclaus commented on code in PR #27192:
URL: https://github.com/apache/camel/pull/27192#discussion_r4155223434
##########
parent/pom.xml:
##########
@@ -370,7 +370,7 @@
<lz4-java-version>1.12.0</lz4-java-version>
<mapstruct-version>1.6.3</mapstruct-version>
<!-- needed from tooling/archetypes -->
- <maven-version>3.9.16</maven-version>
+ <maven-version>3.10.0</maven-version>
Review Comment:
This drives `maven-plugin-api`/`maven-core` for all our Maven plugins, and
maven-plugin-plugin derives each plugin's `requiredMavenVersion` from it
(currently 3.9.16 in the generated plugin.xml). Bumping to 3.10.0 would make
Maven 3.10 mandatory for users of camel-maven-plugin, camel-report-maven-plugin
and the others.
##########
dsl/camel-jbang/camel-launcher/pom.xml:
##########
@@ -48,7 +48,7 @@
<!-- Dependency versions -->
<camel-kamelets-version>4.22.1</camel-kamelets-version>
- <maven-version>3.9.16</maven-version>
+ <maven-version>3.10.0</maven-version>
Review Comment:
camel-launcher ships `maven-resolver-provider:${maven-version}` at compile
scope next to `maven-resolver-api/spi/util:${maven-resolver-version}` (1.9.27).
The 3.10.0 provider is built on Resolver 2.0.24: its
`ValidatingMetadataXpp3Reader` (used by
`DefaultVersionResolver`/`DefaultVersionRangeResolver`) calls
`PathUtils.validatePathComponent`, which is missing from resolver-util 1.9.27,
so a `NoSuchMethodError` is likely when resolving SNAPSHOT or range versions.
--
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]
