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/20 13:14:00 UTC
[jira] [Comment Edited] (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=17620224#comment-17620224 ]
Julian Reschke edited comment on JCR-4860 at 10/20/22 1:13 PM:
---------------------------------------------------------------
Alternatively, we may want to separate modules that *implement* the API from those hat *use* it. The latter could reference earlier versions.
Like that: [^JCR-4860.diff]
[~angela] , [~mreutegg] ?
was (Author: reschke):
Alternatively, we may want to separate modules that *implement* the API from those hat *use* it. The latter could reference earlier versions.
> 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
> Attachments: JCR-4860.diff
>
>
> 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)