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

Posted to dev@sling.apache.org by "Rob Ryan (JIRA)" <ji...@apache.org> on 2014/10/24 01:30:34 UTC

[jira] [Updated] (SLING-2219) SlingAnnotationsTestRunner must use dynamic reference to AnnotationsProcessor

     [ https://issues.apache.org/jira/browse/SLING-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Ryan updated SLING-2219:
----------------------------
    Attachment: SlingAnnotationsTestRunner.patch.txt

Proposed patch which allows SlingAnnotationsTestRunner to continue test execution outside of an OSGI environment. Allowing it to coexist with SlingRemoteExecutionRule.

> SlingAnnotationsTestRunner must use dynamic reference to AnnotationsProcessor
> -----------------------------------------------------------------------------
>
>                 Key: SLING-2219
>                 URL: https://issues.apache.org/jira/browse/SLING-2219
>             Project: Sling
>          Issue Type: Bug
>          Components: Testing
>    Affects Versions: JUnit Core 1.0.6
>            Reporter: Bertrand Delacretaz
>            Assignee: Bertrand Delacretaz
>            Priority: Minor
>             Fix For: JUnit Core 1.0.8
>
>
> The SlingAnnotationsTestRunner's reference to the AnnotationsProcessor can get out of sync if that component goes away, it should be more dynamic. Performance is not really an issue, that's just for integration tests. 



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