[
https://issues.apache.org/jira/browse/JCR-4191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16211084#comment-16211084
]
Julian Reschke commented on JCR-4191:
-------------------------------------
Note that the problem doesn't depend on what compiled the artifact, but only on
what jdk the baseline check is run.
To check
- switch to java 8
- mvn clean install
- mvn bundle:baseline -DcomparisonVersion=2.14.0
...passes.
- switch to java 9
- mvn bundle:baseline -DcomparisonVersion=2.14.0
...fails.
So the choice of the java runtime somehow affects the behavior of
bundle:baseline. My assumption is that under Java 9, it doesn't see the
annotation anymore, although it's there.
> baseline checks fails for jackrabbit-webdav under Java 9
> --------------------------------------------------------
>
> Key: JCR-4191
> URL: https://issues.apache.org/jira/browse/JCR-4191
> Project: Jackrabbit Content Repository
> Issue Type: Sub-task
> Components: jackrabbit-webdav
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Fix For: 2.16
>
>
> with:
> {noformat}
> [INFO] * org.apache.jackrabbit.webdav.lock changed 1.0.0
> 1.0.0 1.0.1 Version increase required
> [INFO] ~ class org.apache.jackrabbit.webdav.lock.Scope
> [INFO] ~ method hashCode()
> [INFO] - annotated jdk.internal.HotSpotIntrinsicCandidate
> {noformat}
> Note that {{hashCode()}} was indeed added for JCR-4100, but why does have
> adding {{hashCode()}} have this effect, and only when the bunde plugin is
> *run* with Java 9?.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
