[
https://issues.apache.org/jira/browse/JCRVLT-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16892720#comment-16892720
]
Julian Reschke commented on JCRVLT-344:
---------------------------------------
I do not plan to remove jackrabbit-api in 2.18, so I would argue that using the
old artefact name is ok as long as Jackrabbit 2.18.* is used.
(It *will* go away in Jackrabbit 2.20).
> update version of jackrabbit and oak dependencies
> --------------------------------------------------
>
> Key: JCRVLT-344
> URL: https://issues.apache.org/jira/browse/JCRVLT-344
> Project: Jackrabbit FileVault
> Issue Type: Task
> Components: Misc
> Reporter: angela
> Priority: Major
> Attachments: JCRVLT-344.patch
>
>
> in order to address JCRVLT-340 the version properties of jackrabbit and oak
> need to be adjusted to use the most recent releases:
> <jackrabbit.version>2.18.2</jackrabbit.version>
> <oak.version>1.16.0</oak.version>
> since there some significant moves made in the code base the following
> additional changes need to follow:
> * adjust dependency _oak-segment_ to _oak-segment-tar_ (the former no longer
> exist)
> - subsequently adjust the changed package names
> (o.a.jackrabbit.oak.plugins.segment.... to o.a.jackrabbit.segment....)
> - adjust dependency _jackrabbit-api_ to use _oak-jackrabbit-api_ as
> jackrabbit-api will no longer be maintained
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
