You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2016/06/02 14:24:59 UTC
[jira] [Updated] (SLING-5679) Move interface Customizer and
customize() from junit.core to junit.teleporter
[ https://issues.apache.org/jira/browse/SLING-5679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus updated SLING-5679:
-----------------------------------
Assignee: (was: Konrad Windszus)
> Move interface Customizer and customize() from junit.core to junit.teleporter
> -----------------------------------------------------------------------------
>
> Key: SLING-5679
> URL: https://issues.apache.org/jira/browse/SLING-5679
> Project: Sling
> Issue Type: Improvement
> Components: Testing
> Affects Versions: JUnit Core 1.0.16, JUnit Tests Teleporter 1.0.6
> Reporter: Konrad Windszus
>
> As discussed in http://www.mail-archive.com/dev@sling.apache.org/msg55732.html the Customizer interface as well as the customize method makes only sense for the client-side of the teleporter rule. Therefore the interface and related methods should be moved from the junit.core to the junit.teleporter module.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)