[
https://issues.apache.org/jira/browse/OAK-4962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15604707#comment-15604707
]
Alex Parvulescu commented on OAK-4962:
--------------------------------------
wouldn't this be as simple as passing the required {{oak-segment-tar}} version
when building {{oak-run}} as a system property? ie.
{noformat}
$ mvn dependency:list | grep segment-tar
[INFO] org.apache.jackrabbit:oak-segment-tar:jar:0.0.16:compile
{noformat}
vs.
{noformat}
$ mvn -Dsegment.tar.version=0.0.17-SNAPSHOT dependency:list | grep segment-tar
[INFO] org.apache.jackrabbit:oak-segment-tar:jar:0.0.17-SNAPSHOT:compile
{noformat}
> Standalone tooling for segment tar
> ----------------------------------
>
> Key: OAK-4962
> URL: https://issues.apache.org/jira/browse/OAK-4962
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: segment-tar
> Reporter: Michael Dürig
> Assignee: Michael Dürig
> Labels: tooling
> Fix For: Segment Tar 0.0.18
>
>
> Currently there is no easy way to run the tools provided by {{oak-run}}
> against a snapshot version of Segment Tar. In order to have better CI
> coverage (e.g. benchmarks) of Segment Tar, we need to introduce a way for
> running such tools independently of {{oak-run}}. Eventually {{oak-run}}
> should even be using that tooling front-end instead of directly depending on
> {{oak-segment-tar}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
