[ 
https://issues.apache.org/jira/browse/OAK-11645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julian Reschke updated OAK-11645:
---------------------------------
    Description: 
When we introduced shaded Guava (OAK-9989), we decided for simplicity to use 
the Guava version for our package versions. So for Guava 33.4.0, we just 
exported all packages with package version 33.4.0.

Lately, Google has switched nullability annotations (from javax to 
https://jspecify.dev/), which cause baseline errors, because changing 
annotations changes the API (from bnd's point of view).

Problem: in Guava versions, these changes happen in PATCH releases (which is 
fine, because they do not use semantic versioning (properly)).

Solution: change package version to something we control.

  was:
When we introduced shaded Guava (OAK-9989), we decided for simplicity to used 
the Guava version for our package versions.

Lately, Google has switched nullability annotations (https://jspecify.dev/), 
which cause baseline errors.

Solution: change package version to something we control.


> take over package versions for shaded guava
> -------------------------------------------
>
>                 Key: OAK-11645
>                 URL: https://issues.apache.org/jira/browse/OAK-11645
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: shaded-guava
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>            Priority: Major
>
> When we introduced shaded Guava (OAK-9989), we decided for simplicity to use 
> the Guava version for our package versions. So for Guava 33.4.0, we just 
> exported all packages with package version 33.4.0.
> Lately, Google has switched nullability annotations (from javax to 
> https://jspecify.dev/), which cause baseline errors, because changing 
> annotations changes the API (from bnd's point of view).
> Problem: in Guava versions, these changes happen in PATCH releases (which is 
> fine, because they do not use semantic versioning (properly)).
> Solution: change package version to something we control.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to