[
https://issues.apache.org/jira/browse/SLING-5067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-5067.
-----------------------------------
Resolution: Fixed
i can confirm we have a problem here with threads not terminated, even in
sling-mock alone without oak. i've created SLING-5088 to track it - i'm quite
sure it's not related to this issue, perhaps the issue was only that the number
of unit tests increased.
setting this feature ticket to fixed again.
> sling-mock: "uniqueRoot()" to simplify creation and cleanup of unique root
> paths in repository
> ----------------------------------------------------------------------------------------------
>
> Key: SLING-5067
> URL: https://issues.apache.org/jira/browse/SLING-5067
> Project: Sling
> Issue Type: New Feature
> Components: Testing
> Affects Versions: Testing Sling Mock 1.5.0
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Labels: mocks
> Fix For: Testing Sling Mock Jackrabbit 1.0.0, Testing Sling Mock
> Oak 1.0.0, Testing Sling Mock 1.6.0
>
>
> when using resource resolver types JCR_JACKRABBIT and JCR_OAK unique root
> paths have to be used because the repository is not cleaned up after each
> run, and esp. if unit tests run in parallel.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
