You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Julian Reschke (Jira)" <ji...@apache.org> on 2022/10/18 12:26:00 UTC

[jira] [Commented] (JCR-4860) jcr-commons in 2.20 can not be used with Oak 1.22.x

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

Julian Reschke commented on JCR-4860:
-------------------------------------

[~mreutegg], [~angela] - what do you think?

Proposed patch:
{noformat}
Index: jackrabbit-jcr-commons/pom.xml
===================================================================
--- jackrabbit-jcr-commons/pom.xml      (revision 1904678)
+++ jackrabbit-jcr-commons/pom.xml      (working copy)
@@ -75,6 +75,7 @@
     <dependency>
       <groupId>org.apache.jackrabbit</groupId>
       <artifactId>oak-jackrabbit-api</artifactId>
+      <version>1.22.13</version>
       <optional>true</optional>
     </dependency>
     <dependency>
{noformat}

> jcr-commons in 2.20 can not be used with Oak 1.22.x
> ---------------------------------------------------
>
>                 Key: JCR-4860
>                 URL: https://issues.apache.org/jira/browse/JCR-4860
>             Project: Jackrabbit Content Repository
>          Issue Type: Task
>          Components: jackrabbit-jcr-commons
>    Affects Versions: 2.20.6
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>            Priority: Major
>
> This is because Jackrabbit 2.20 uses oak-jackrabbit-api (latest stable), but Oak 1.22 does not.
> In practice, jcr-commons does not need the more recent API extensions, so the simplest possible fix seems to hard-wire an earlier version of oak-jackrabbit-api into the jcr-commons dependencies.



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