dmlloyd commented on issue #7257: URL: https://github.com/apache/camel-quarkus/issues/7257#issuecomment-2801754406
On 2025-03-25, there was a dependabot update to the `quarkus-jgit` Quarkiverse project to update `jgit` from version `7.1.0.202411261347-r` to `7.2.0.202503040940-r`. As a part of this change, @gastaldi changed the class name strings used to register things for reflection to direct class references. This change was included in versions `3.4.0` and later of this extension. The public class in question - `org.eclipse.jgit.dircache.DirCache.DirCacheVersion` - is marked as `@since 7.2`. Prior to this version, the class in question existed, but was marked package-private. Accessing this (package-private) class in this way (as if it were public) would result in exactly the error & stack seen above. So, I infer that this access error is occurring because the `quarkus-jgit` extension version is mismatched with respect to the version of `jgit` itself. It looks like the `camel-quarkus` extension is using version `3.3.3` of `quarkus-jgit`. However, something in the dependency graph must be using a newer version. Because of Maven's... "unusual"... resolution logic, transitive dependency versions are (usually) determined more strongly by closeness to the "root" of the dependency tree rather than a less surprising algorithm (such as latest-always-wins). The quick fix would be to update the `quarkus-jgit` extension, or to explicitly manage the version of `jgit` to match what `quarkus-jgit` is expecting. It would be a good idea to do some dependency analysis and figure out why you are getting conflicting versions of `quarkus-jgit` though. -- 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: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
