You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2016/03/31 16:06:25 UTC

[jira] [Commented] (SLING-5571) Integration tests using SlingRepositoryInitializer fail

    [ https://issues.apache.org/jira/browse/SLING-5571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219903#comment-15219903 ] 

Bertrand Delacretaz commented on SLING-5571:
--------------------------------------------

For the above I had to disable all tests that depend on the SLING-5456 {{SlingRepositoryInitializer}} feature in revision 1732909

I tried to reactivate those today but the oak.server bundle doesn't start if using the required jcr.base and jcr.api snapshots, due to the SLING-5537 changes to {{AbstractSlingRepositoryManager}} in jcr.base.

For now I have asked on our dev list how to handle those changes.

> Integration tests using SlingRepositoryInitializer fail
> -------------------------------------------------------
>
>                 Key: SLING-5571
>                 URL: https://issues.apache.org/jira/browse/SLING-5571
>             Project: Sling
>          Issue Type: Bug
>          Components: Testing
>            Reporter: Bertrand Delacretaz
>            Assignee: Bertrand Delacretaz
>            Priority: Minor
>
> Changes to the jcr.api 2.3.1-SNAPSHOT have modified the import of that bundle and it does not start, causing a number of tests to fail. Trying to fix that requires updating many bundles, so as a first step I'll revert to jcr.api 2.3.0 and disable the corresponding tests.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)