[
https://issues.apache.org/jira/browse/OAK-7182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17629845#comment-17629845
]
Julian Reschke commented on OAK-7182:
-------------------------------------
Well; progress is on this issue proves to be hard.
We sort-of had settled to first deprecating and then removing APIs that expose
Guava objects. We were done with the deprecations, but a certain downstream
project hasn't been updated yet, and doing so will take time.
OTOH, we planned to revise Oak's code to use newer versions of Gauva in any
case (be it directly or shadowed - both will require code changes).
So my proposal is to - while we're waiting on progress on the
deprecation/removal front - we actually start upgrading Guava step by step. For
now that would mean moving to 19.0, which would allow us to update our code not
to use those APIs that have been removed ib Guava >= 20.0.
Feedback appreciated.
> Make it possible to update Guava
> --------------------------------
>
> Key: OAK-7182
> URL: https://issues.apache.org/jira/browse/OAK-7182
> Project: Jackrabbit Oak
> Issue Type: Wish
> Reporter: Julian Reschke
> Priority: Minor
> Attachments: GuavaTests.java, OAK-7182-guava-21-3.diff,
> OAK-7182-guava-21-4.diff, OAK-7182-guava-21.diff, OAK-7182-guava-23.6.1.diff,
> guava.diff
>
>
> We currently rely on Guava 15, and this affects all users of Oak because they
> essentially need to use the same version.
> This is an overall issue to investigate what would need to be done in Oak in
> order to make updates possible.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
