[
https://issues.apache.org/jira/browse/OAK-4650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Mari resolved OAK-4650.
---------------------------------
Resolution: Fixed
Fix Version/s: (was: Segment Tar 0.0.16)
Segment Tar 0.0.12
Solving this issue as fixed. Since version 0.0.10, utility code is part of
oak-segment-tar. oak-run has been updated to use oak-segment-tar instead of
maintaining its own copy of the utility code. The change will be visible
starting from Oak 1.5.9.
> Move utility code from oak-run into oak-segment-tar
> ---------------------------------------------------
>
> Key: OAK-4650
> URL: https://issues.apache.org/jira/browse/OAK-4650
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar
> Reporter: Francesco Mari
> Assignee: Francesco Mari
> Fix For: Segment Tar 0.0.12
>
>
> Utility code for oak-segment-tar can be currently accessed only from oak-run
> or, at least, this is what we recommend to our users.
> It is very difficult to detect which version of oak-segment-tar is embedded
> in oak-run and this can create confusion when users try to run utility code
> for a specific version of the segment store.
> I propose to move utility code related to oak-segment-tar into the bundle
> itself. It should be possible to run this code from the JAR of
> oak-segment-tar, without resorting to oak-run. Utility code from
> oak-segment-tar can still be referenced from and embedded into oak-run, with
> the usual constraint of the {{--segment-tar}} command line option, even if I
> wouldn't recommend this anymore.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
