[
https://issues.apache.org/jira/browse/OAK-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15446299#comment-15446299
]
Tomek Rękawek commented on OAK-4718:
------------------------------------
[~frm], it's the out-of-the-box Apache Sling repository. Taking Sling was the
simplest way to have a non-trivial repository (close to the production ones)
that can be used in the oak-upgrade tests. However, storing a binary package
which format depends on the code changes is indeed an unfortunate solution.
As workaround (so you can proceed with your work), I've changed the
segmenstore.zip format to the old SegmentMK and adjusted the testing code
accordingly. Will that work for you?
Change was done in [r1758253|https://svn.apache.org/r1758253].
> Tests in oak-upgrade depend on an archived repository
> -----------------------------------------------------
>
> Key: OAK-4718
> URL: https://issues.apache.org/jira/browse/OAK-4718
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: upgrade
> Reporter: Francesco Mari
> Assignee: Tomek Rękawek
> Fix For: 1.6
>
>
> The tests in oak-upgrade don't generate test content on the fly, but rely on
> a segment store archived in {{segmentstore.zip}}. This forces this content to
> be rebuilt every time there is a change in the binary format or in the
> segment store metadata at large. Tests in oak-uprade should generate test
> content on the fly, or it should be obvious how to upgrade this repository
> every time it is needed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
