You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2015/10/05 10:58:28 UTC

[jira] [Comment Edited] (SLING-5088) sling-mock: Threads created by resource resolver/JCR are not terminated properly

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

Robert Munteanu edited comment on SLING-5088 at 10/5/15 8:58 AM:
-----------------------------------------------------------------

Looks good to me now, thank you!


was (Author: rombert):
Looks good to me know, thank you!

> sling-mock: Threads created by resource resolver/JCR are not terminated properly
> --------------------------------------------------------------------------------
>
>                 Key: SLING-5088
>                 URL: https://issues.apache.org/jira/browse/SLING-5088
>             Project: Sling
>          Issue Type: Bug
>          Components: Testing
>    Affects Versions: Testing Sling Mock Jackrabbit 0.1.2, Testing Sling Mock 1.5.0
>            Reporter: Stefan Seifert
>            Assignee: Stefan Seifert
>            Priority: Critical
>              Labels: mocks
>             Fix For: Testing Sling Mock Jackrabbit 1.0.0, Testing Sling Mock Oak 1.0.0, Testing OSGi Mock 1.6.0, Testing Sling Mock 1.6.0
>
>
> as detected in SLING-5067 threads that are opened during unit test run when setting up resource resolver with JCR mapping for the mocks are not terminated properly and may lead to problems if the number of unit tests increases.



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