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 2017/10/02 12:46:00 UTC
[jira] [Updated] (SLING-7166) Deprecate Commons Testing
[ https://issues.apache.org/jira/browse/SLING-7166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus updated SLING-7166:
-----------------------------------
Description:
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}}: should be moved to org.apache.sling.testing.rules, but already mostly covered by the Sling HTTP Testing Client
# {{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.
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/dev@sling.apache.org/msg70983.html.
was:
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}} should be used
# {{o.a.s.commons.testing.jcr}}: jcr-mock should be used instead
# {{o.a.s.commons.testing.junit}}: should be moved to org.apache.sling.testing.rules
# {{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.
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/dev@sling.apache.org/msg70983.html.
> 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
> Fix For: Commons Testing 2.1.4
>
>
> 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}}: should be moved to org.apache.sling.testing.rules, but already mostly covered by the Sling HTTP Testing Client
> # {{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.
> 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/dev@sling.apache.org/msg70983.html.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)