[
https://issues.apache.org/jira/browse/SLING-12582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17906710#comment-17906710
]
Stefan Seifert commented on SLING-12582:
----------------------------------------
i've never used https://github.com/apache/sling-org-apache-sling-junit-remote
myself, but some comments from my side:
* in case there is a need to revive it and bring it to junit 5, it's probably
better to either start a new project for junit 5, or dropping the junit 4
support altogether.
* having code in one project in parallel makes the code overcomplicated, and
esp. difficult with code dependency management (been there with sling mock &
co).
* it looks as junit.remote was very inactive in the last years (last release 7
years ago), so the the junit 4 support could be probably dropped completely,
and a new major version with junit 5 could be created.
> Migrate junit.remote to also work on junit5
> -------------------------------------------
>
> Key: SLING-12582
> URL: https://issues.apache.org/jira/browse/SLING-12582
> Project: Sling
> Issue Type: Improvement
> Reporter: Roy Teeuwen
> Priority: Major
>
> Currently the implementation of junit.remote uses @Rule, which is only
> available in junit4 and no longer in junit5. We should devise a way to make
> the junit.remote also work on junit5
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
