[
https://issues.apache.org/jira/browse/SLING-7166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18046552#comment-18046552
]
Stefan Seifert commented on SLING-7166:
---------------------------------------
i agree we should get rid of that library. but we did not manage to do that in
the last 8 years since creation of this ticket, and it' still quite in use,
although a couple of that repos are also unmaintained by now:
[https://github.com/search?q=org%3Aapache+org.apache.sling.commons.testing+language%3A%22Maven+POM%22&type=code&l=Maven+POM]
in the meantime, to keep it alive for the integration tests we have in place, a
did a bit of dependency updates in SLING-13036
> Deprecate Commons Testing
> -------------------------
>
> Key: SLING-7166
> URL: https://issues.apache.org/jira/browse/SLING-7166
> Project: Sling
> Issue Type: Improvement
> Components: Testing
> Affects Versions: Commons Testing 2.1.2
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: Commons Testing 2.2.2
>
>
> The module {{Commons Testing}} seems to be rather old and not too actively
> maintained. For most (if not all) of its classes there are nowadays better
> replacements:
> For the individual packages I consider the following alternatives the better
> choices
> # {{o.a.s.commons.testing.integration}}: Teleporter or the
> [org.apache.sling.testing.clients|https://github.com/apache/sling/tree/trunk/testing/http/clients]
> should be used preferably instantiated through [Sling HTTP testing
> rules|https://github.com/apache/sling/tree/trunk/testing/junit/rules].
> # {{o.a.s.commons.testing.jcr}}: jcr-mock should be used instead
> # {{o.a.s.commons.testing.junit}}: the retry logic from the [Sling HTTP
> Testing
> Client|https://github.com/apache/sling/tree/trunk/testing/http/clients]
> should be used.
> # # {{o.a.s.commons.testing.junit.categories}}:
> {{o.a.s.testing.junit.rules.category.SlowRunningTest}} from [Sling HTTP
> testing
> rules|https://github.com/apache/sling/tree/trunk/testing/junit/rules]. should
> be used instead.
> # {{o.a.s.commons.testing.osgi}}: osgi-mock should be used instead
> # {{o.a.s.commons.testing.sling}}: sling-mock should be used instead
> # {{org.apache.sling.commons.testing.util}}: if really useful can maybe moved
> to sling-mock as well, but probably not that useful. Currently
> {{TestStringUtil}} is [not used at
> all|https://github.com/apache/sling/search?utf8=%E2%9C%93&q=TestStringUtil.&type=]
> and {{JavascriptEngine}} is only used from
> {{o.a.s.commons.testing.integration}}.
> In addition there are certain limitations in that module which are not easy
> to fix:
> # {{o.a.s.commons.testing.jcr}} uses Jackrabbit 2 only and never Oak, that
> means that the ITs based on those classes are pretty far away from what we
> ship now in Sling.
> # {{o.a.s.commons.testing.jcr}} is currently not compatible with Java 9
> (https://issues.apache.org/jira/browse/SLING-7159)
> The according discussion around this can be found in
> https://www.mail-archive.com/[email protected]/msg70983.html.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
