Details
Description
The Customer is trying to upgrade Mockito to a newer version of their project.
Currently, they are on Mockito version 4.4.0, which holds a dependency on bytebuddy version 1.12.8, and from Mockito 4.5.0 onwards, it holds a dependency on bytebuddy version 1.12.9. The difference between these minor versions of Byte Buddy is that the newer version contains a class that is required in Mockito 4.5.0 to successfully execute unit tests.
However, the library org.onehippo.cms7.hst:hst:15.4.0 declares a dependency on bytebuddy 1.10.2 (released on Oct 16, 2019). When Maven resolves all the dependencies in the project, this version is used. This conflicts with the required version of bytebuddy 1.12.9 for Mockito 4.5.0.
In other words, they cannot upgrade Mockito to a newer version, unless they also declare a dependency on bytebuddy 1.12.9. This would override the version declared in org.onehippo.cms7.hst:hst:15.4.0, which would mean that Bloomreach will also use this version, despite that it has not been tested with this version.
Preferably Client would want Bloomreach to dictate the required versions of common libraries. But that also means that these have to be upgraded from time to time. That is for org.onehippo.cms7.hst:hst not the case.
The customer asking if would it be possible to, for example in version 15.5.0, upgrade this third-party library in org.onehippo.cms7.hst:hst? So that we can upgrade Mockito to a newer version?
Attachments
Issue Links
- relates to
-
CMS-15997 Bump dependencies
- Closed