[
https://issues.apache.org/jira/browse/JCR-4191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209956#comment-16209956
]
Karl Pauls commented on JCR-4191:
---------------------------------
[~reschke], I think it is not adding the hashCode method (that is always
there). It is the jdk.internal.HotSpotIntrinsicCandidate annotation that java9
will add automagically. That will be picked up by bnd as a micro change.
Normally, I would say that is correct and you should just bump the version
number but in this case that would be bad because it would flip-flop
dependening on the java version used to build the bundle.
Regarding your test using bnd directly: did you maybe build
target/jackrabbit-webdav-2.15.7-SNAPSHOT.jar with java8? I don't think it is
important which java version you use to run bnd but rather which one you use to
build the SNAPSHOT.
> 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 tools is run with
> Java 9.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
