allthingssecurity commented on PR #28263:
URL: https://github.com/apache/camel/pull/28263#issuecomment-6335458917
Thanks Claus, good catch. Fixed in d59f575d82 (and the same change in
#28262, 252c279e3b).
I compared the trees in components/camel-xmpp: locally the default resolver
and `-Daether.dependencyCollector.impl=bf` give the same result, and both have
`jxmpp-util-cache`. The verbose tree shows why the versions are odd: smack-core
4.4.8 asks for jxmpp-core and jxmpp-jid in the range `[1.0.0,1.0.999]`, so our
direct `jxmpp-jid:1.1.0` is "omitted for conflict with 1.0.3" and the build
really uses jxmpp 1.0.3 (the SBOM agrees). So I could not reproduce the CI
classpath here, but `org/jxmpp/util/cache/Cache` only comes in through that
range-resolved jxmpp-core, which fits your guess about mvnd's resolver.
The commit declares `jxmpp-util-cache` next to `jxmpp-jid` with the same
`${jxmpp-version}`, so it is on the classpath whatever the resolver does. With
it the tree has jxmpp-jid/jxmpp-core 1.0.3 and jxmpp-util-cache 1.1.0 (the
`Cache` classes are the same in both). camel-xmpp unit tests with
`-Daether.dependencyCollector.impl=bf`: 14 run, 0 failures, 5 skipped here (20
run on #28262).
Separately, the 1.1.0 in `jxmpp-version` has never been used because of
Smack's range; aligning the property with what Smack 4.4.x accepts would be a
follow-up, not this PR.
_Claude Code on behalf of allthingssecurity_
--
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]
