[
https://issues.apache.org/jira/browse/OAK-7182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16344786#comment-16344786
]
Robert Munteanu commented on OAK-7182:
--------------------------------------
Thinking about how to best 'break away' from a specific Guava version, here's
my proposal (not tested):
# minimize API exposure from Guava
# replace all Guava usages where alternatives from the JDK exist
# inline Guava in the bundles that import it using {{Conditional-Package}}
# import the Guava packages that we use in the API with a wide, open-ended
range, e.g. {{[15,)}}
This might work since it allows us to depend on a 'private' version of Guava
but the APIs will work with other version as well. I am not sure whether we'll
run into uses constraints due to the Oak bundle importing different versions of
Guava at some point.
> 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: 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)
