[
https://issues.apache.org/jira/browse/OAK-7182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16779127#comment-16779127
]
Julian Reschke edited comment on OAK-7182 at 9/11/19 8:27 AM:
--------------------------------------------------------------
It might be an option to create a custom API (owned by Oak) in a separate
bundle. This bundle would be the only one allowed to import Guava. Furthermore,
there may be multiple implementations of the API. E.g. one using Guava 15,
another using Guava 25 and possibly later an implementation owned entirely by
Oak.
In order to be able to update Guava in an OSGi container only the matching
implementation of this Oak API would need to be deployed.
This solution would allow for a gradual transition away from Guava while easing
the pain immediately.
WDYT?
was (Author: jsedding):
It might be an option to create a custom API (owned by Oak) in a separate
bundle. This bundle would be the only one alloed to import Guava. Furthermore,
there may be multiple implementations of the API. E.g. one using Guava 15,
another using Guava 25 and possibly later an implementation owned entirely by
Oak.
In order to be able to update Guava in an OSGi container only the matching
implementation of this Oak API would need to be deployed.
This solution would allow for a gradual transition away from Guava while easing
the pain immediately.
WDYT?
> 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
(v8.3.2#803003)
