On 11.08.2023 11:39, Julian Reschke wrote:
...
Oak itself is now independent of native Guava, but we still use test
tooling that pulls it in (see OAK-10367). Depending on how we resolve
this, we could then remove the remains from config and POMs.
In the meantime, that was fixed by Manfred (thanks!).
However, we have an azure-sdk dependency that transitively pulls in
Guava (see https://issues.apache.org/jira/browse/OAK-10371).
Fortunately, there's a major update to the SDK which does not seem to
use Guava anymore.
...
So, with the release of 1.56.0 last week, this is the only remaining
issue that ties (parts of) Oak to Guava. I believe this should be fixed
in the next release (even if we take the simple way of just embedding it).
If have set the "fixVersion" for OAK-10371 to 1.58.0; can somebody from
the segment persistence experts please have a look ASAP?
Best regards, Julian
