You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-dev@jackrabbit.apache.org by Julian Reschke <ju...@gmx.de> on 2023/07/26 06:28:58 UTC
Re: Guava Migration (yes, a must read)
On 12.06.2023 15:50, Julian Reschke wrote:
> ...
> We have made good progress, but as usual, things take longer than expected.
>
> We have a pending PR for fixing oak-commons
> (https://issues.apache.org/jira/browse/OAK-10247), but I could not apply
> it yet (due to the current status of a certain downstream project).
>
> The current plan is to cut 1.54.0 once this has been done (early July),
> and then do the remaining changes in 1.56.0.
> ...
Champagne (sort of).
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.
Best regards, Julian
Re: Guava Migration (yes, a must read)
Posted by Julian Reschke <ju...@gmx.de>.
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
Re: Guava Migration (yes, a must read)
Posted by Julian Reschke <ju...@gmx.de>.
On 26.07.2023 08:28, Julian Reschke wrote:
> On 12.06.2023 15:50, Julian Reschke wrote:
>> ...
>> We have made good progress, but as usual, things take longer than
>> expected.
>>
>> We have a pending PR for fixing oak-commons
>> (https://issues.apache.org/jira/browse/OAK-10247), but I could not apply
>> it yet (due to the current status of a certain downstream project).
>>
>> The current plan is to cut 1.54.0 once this has been done (early July),
>> and then do the remaining changes in 1.56.0.
>> ...
>
> Champagne (sort of).
>
> 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.
Best regards, Julian