davsclaus opened a new pull request, #27290:
URL: https://github.com/apache/camel/pull/27290
The curated known third-party libraries in `camel-kamelet-main`
(CAMEL-24809) mapped:
```properties
com.bazaarvoice.jolt = com.bazaarvoice.jolt:jolt-core:${jolt-version}
```
That was correct when `jolt-version` was `0.1.8`. CAMEL-24806 then switched
`camel-jolt` to the jolt-community fork and set `jolt-version` to `1.3.0`. The
mapping now pointed to `com.bazaarvoice.jolt:jolt-core:1.3.0`, which doesn't
exist (404 on Maven Central; the last bazaarvoice release is 0.1.8). The fork's
package, `io.joltcommunity.jolt`, which `camel-jolt` imports, wasn't mapped at
all.
The normal build doesn't catch this: it only checks that the version
property exists. The opt-in `-Dcamel.known-dependencies.verify=true` failed on
it.
## Change
```properties
io.joltcommunity.jolt =
io.github.jolt-community.jolt:jolt-community-core:${jolt-version}
```
The old `com.bazaarvoice.jolt` entry is dropped: Camel no longer uses that
library, and the curated list doesn't allow a literal version.
## Tests
-
`KnownDependenciesResolverTest#theShippedMappingResolvesThirdPartyClassesByPackage`
checks `io.joltcommunity.jolt.Chainr` → `jolt-community-core`.
- `mvn install -Dcamel.known-dependencies.verify=true` in
`camel-kamelet-main` passes again: every curated library resolves, and its
package is in the jar.
_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]
