[ 
https://issues.apache.org/jira/browse/OAK-7182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17558382#comment-17558382
 ] 

Julian Reschke commented on OAK-7182:
-------------------------------------

bq. Depend on 22.0 Guava

It sounds plausible, but my recollection is that we decided to erase Guava from 
our exported APIs. When we have done that, the question whether we use Guava, 
and if so how (directly, or by shading it) becomes secondary.

Of course more discussion is good; in essence it's about how much we want to 
trust Guava's evolution (and whether it's even needed given evolution of JDKs).

> 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.7#820007)

Reply via email to