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

Robert Munteanu commented on OAK-7182:
--------------------------------------

I am looking into the Guava packaging and release policy, and it seems that 
they have started following semantic versioning - 
https://github.com/google/guava/wiki/ReleasePolicy . In particular, they will 
only upgrade the major version "
If there are API removals or other incompatible API changes", and that includes 
APIs annotated with {{\@Beta}} . Which in turn for us this means that once we 
incorporate a new version of Guava we should be safe for a longer time. They do 
have breaking changes, for instance this year they had 3 major releases ( and 6 
minor ones ) but version 23 is now 23.6, which may mark a turn in how they 
approach backwards compatibility.

What we can do is either "vet" certain versions, e.g. test with Guava 15 and 
latest ( 23.6 ) and adjust the import versions to be [15,24). Or alternatively 
hope for the test and import [15,).

> 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)

Reply via email to