[
https://issues.apache.org/jira/browse/OAK-7182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16772778#comment-16772778
]
Julian Reschke commented on OAK-7182:
-------------------------------------
bq. I have come to strongly believe that any leak of Guava APIs in the Oak
codebase - whether it's in exported API or not - is a risk.
Not that I disagree, but could you clarify why it's a problem for non-exported
APIs?
bq. ... or by importing it statically and shading it (optional rant below).
Shading is a problem because of the size, unless we create a separate Oak
module which does nothing except shading all of Guava.
...at the end of the day, we'll have to figure out what to do with the exported
APIs that currently *do* leak Guava APIs.
> 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
> Assignee: 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
(v7.6.3#76005)
