[
https://issues.apache.org/jira/browse/OAK-7182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16772838#comment-16772838
]
Robert Munteanu commented on OAK-7182:
--------------------------------------
{quote}Not that I disagree, but could you clarify why it's a problem for
non-exported APIs?{quote}
I consider it a problem because we have seem multiple times that Guava APIs
change in backwards incompatible ways. The smaller the exposure we have to
Guava APIs, the easier it is for us to support multiple Guava versions.
{quote}Shading is a problem because of the size, unless we create a separate
Oak module which does nothing except shading all of Guava.{quote}
I would hope that we don't need all of Guava. But yes, size is an issue,
together with the issue of customers depending on updating Oak to get newer
Guava versions - but I guess this is the current situation anyway.
> 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)
