[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}}: 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/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|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=]
is not used at all.
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
&g
[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}}: 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=]
is not used at all.
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|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.
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/t
[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}}: 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.
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|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.
> 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}}: 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}} fro
[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
[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}} 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.
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.
Apart from that there are IMHO better alternatives for all those classes
available, there are certain limitations which are IMHO 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}} 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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[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}} 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.
Apart from that there are IMHO better alternatives for all those classes
available, there are certain limitations which are IMHO 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.
Apart from that there are IMHO better alternatives for all those classes
available, there are certain limitations which are IMHO 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}} 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.
> Apart from that there are IMHO better alternatives for all those classes
> available, there are certain limitations which are IMHO 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)
[jira] [Created] (SLING-7166) Deprecate Commons Testing
Konrad Windszus created SLING-7166:
--
Summary: 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
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.
Apart from that there are IMHO better alternatives for all those classes
available, there are certain limitations which are IMHO 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)
[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:
---
Fix Version/s: Commons Testing 2.1.4
> 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}}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.
> Apart from that there are IMHO better alternatives for all those classes
> available, there are certain limitations which are IMHO 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)
Re: Deprecate Commons Testing?
+ 1 & +1 to stefan's suggestions Regards Julian On Thu, Sep 28, 2017 at 6:07 PM, Stefan Seifert wrote: > +1 > > perhaps we can start making a new release with all classes deprecated, and > updating pom references to this. > then it's easier to find it's usage and replace it when one touches a module. > replacing all usages at once will be too tedious because the alternatives are > not drop-in replacements. > > stefan > >>-Original Message- >>From: Konrad Windszus [mailto:konra...@gmx.de] >>Sent: Thursday, September 28, 2017 1:03 PM >>To: dev@sling.apache.org >>Subject: Deprecate Commons Testing? >> >>Currently Commons Testing can be found in bundles/commons/testing >>(https://github.com/apache/sling/tree/trunk/bundles/commons/testing) >>although I would rather expect it below testing >>(https://github.com/apache/sling/tree/trunk/testing) in SVN. >>Apart from that library seems to be rather old and not too actively >>maintained. For most of its classes there are nowadays better replacements: >> >>Package >>1. o.a.s.commons.testing.integration: Rather either Teleporter or the >>org.apache.sling.testing.clients should be used >>2. o.a.s.commons.testing.jcr: jcr-mock should be used instead >>3. o.a.s.commons.testing.junit: should be converted to rules >>(org.apache.sling.testing.rules) >>4. o.a.s.commons.testing.osgi: osgi-mock should be used instead >>5. o.a.s.commons.testing.sling: sling-mock should be used instead >>6. org.apache.sling.commons.testing.util: if really useful can maybe moved >>to sling-mock as well >> >>Apart from that there are IMHO better alternatives for all those classes >>available, there are certain limitations which are IMHO not easy to fix: >> >>1. o.a.s.commons.testing.jcr uses Jackrabbit 2 only and never Oak, that >>means that the ITs are pretty far away from what we ship now in Sling. >>2. o.a.s.commons.testing.jcr is currently not compatible with Java 9 >>(https://issues.apache.org/jira/browse/SLING-7159) >> >>WDYT? >>Should we add deprecation hints to all those classes pointing to the better >>alternatives and spin a last release? >> >>Currently we have way too many alternatives when it comes to testing >>support and focusing only on one way of doing things certainly helps to >>reduce the maintenance effort. >>The next candidate to deprecate would be Testing Tools... >> >>Konrad >
RE: Deprecate Commons Testing?
+1 perhaps we can start making a new release with all classes deprecated, and updating pom references to this. then it's easier to find it's usage and replace it when one touches a module. replacing all usages at once will be too tedious because the alternatives are not drop-in replacements. stefan >-Original Message- >From: Konrad Windszus [mailto:konra...@gmx.de] >Sent: Thursday, September 28, 2017 1:03 PM >To: dev@sling.apache.org >Subject: Deprecate Commons Testing? > >Currently Commons Testing can be found in bundles/commons/testing >(https://github.com/apache/sling/tree/trunk/bundles/commons/testing) >although I would rather expect it below testing >(https://github.com/apache/sling/tree/trunk/testing) in SVN. >Apart from that library seems to be rather old and not too actively >maintained. For most of its classes there are nowadays better replacements: > >Package >1. o.a.s.commons.testing.integration: Rather either Teleporter or the >org.apache.sling.testing.clients should be used >2. o.a.s.commons.testing.jcr: jcr-mock should be used instead >3. o.a.s.commons.testing.junit: should be converted to rules >(org.apache.sling.testing.rules) >4. o.a.s.commons.testing.osgi: osgi-mock should be used instead >5. o.a.s.commons.testing.sling: sling-mock should be used instead >6. org.apache.sling.commons.testing.util: if really useful can maybe moved >to sling-mock as well > >Apart from that there are IMHO better alternatives for all those classes >available, there are certain limitations which are IMHO not easy to fix: > >1. o.a.s.commons.testing.jcr uses Jackrabbit 2 only and never Oak, that >means that the ITs are pretty far away from what we ship now in Sling. >2. o.a.s.commons.testing.jcr is currently not compatible with Java 9 >(https://issues.apache.org/jira/browse/SLING-7159) > >WDYT? >Should we add deprecation hints to all those classes pointing to the better >alternatives and spin a last release? > >Currently we have way too many alternatives when it comes to testing >support and focusing only on one way of doing things certainly helps to >reduce the maintenance effort. >The next candidate to deprecate would be Testing Tools... > >Konrad
Re: Deprecate Commons Testing?
Hi, On Thu, 2017-09-28 at 13:03 +0200, Konrad Windszus wrote: > Currently Commons Testing can be found in bundles/commons/testing (ht > tps://github.com/apache/sling/tree/trunk/bundles/commons/testing) > although I would rather expect it below testing (https://github.com/a > pache/sling/tree/trunk/testing) in SVN. > Apart from that library seems to be rather old and not too actively > maintained. For most of its classes there are nowadays better > replacements: > > Package > 1. o.a.s.commons.testing.integration: Rather either Teleporter or the > org.apache.sling.testing.clients should be used > 2. o.a.s.commons.testing.jcr: jcr-mock should be used instead > 3. o.a.s.commons.testing.junit: should be converted to rules > (org.apache.sling.testing.rules) > 4. o.a.s.commons.testing.osgi: osgi-mock should be used instead > 5. o.a.s.commons.testing.sling: sling-mock should be used instead > 6. org.apache.sling.commons.testing.util: if really useful can maybe > moved to sling-mock as well > > Apart from that there are IMHO better alternatives for all those > classes available, there are certain limitations which are IMHO not > easy to fix: > > 1. o.a.s.commons.testing.jcr uses Jackrabbit 2 only and never Oak, > that means that the ITs are pretty far away from what we ship now in > Sling. > 2. o.a.s.commons.testing.jcr is currently not compatible with Java 9 > (https://issues.apache.org/jira/browse/SLING-7159) > > WDYT? > Should we add deprecation hints to all those classes pointing to the > better alternatives and spin a last release? > > Currently we have way too many alternatives when it comes to testing > support and focusing only on one way of doing things certainly helps > to reduce the maintenance effort. +1 I suggest to also create tasks for: - removing usages from within Sling - updating the documentation to reflect this status Of course, reviewing the modules that use this library would also reveal if we have any gaps that the other libraries don't cover. Thanks, Robert
Deprecate Commons Testing?
Currently Commons Testing can be found in bundles/commons/testing (https://github.com/apache/sling/tree/trunk/bundles/commons/testing) although I would rather expect it below testing (https://github.com/apache/sling/tree/trunk/testing) in SVN. Apart from that library seems to be rather old and not too actively maintained. For most of its classes there are nowadays better replacements: Package 1. o.a.s.commons.testing.integration: Rather either Teleporter or the org.apache.sling.testing.clients should be used 2. o.a.s.commons.testing.jcr: jcr-mock should be used instead 3. o.a.s.commons.testing.junit: should be converted to rules (org.apache.sling.testing.rules) 4. o.a.s.commons.testing.osgi: osgi-mock should be used instead 5. o.a.s.commons.testing.sling: sling-mock should be used instead 6. org.apache.sling.commons.testing.util: if really useful can maybe moved to sling-mock as well Apart from that there are IMHO better alternatives for all those classes available, there are certain limitations which are IMHO not easy to fix: 1. o.a.s.commons.testing.jcr uses Jackrabbit 2 only and never Oak, that means that the ITs are pretty far away from what we ship now in Sling. 2. o.a.s.commons.testing.jcr is currently not compatible with Java 9 (https://issues.apache.org/jira/browse/SLING-7159) WDYT? Should we add deprecation hints to all those classes pointing to the better alternatives and spin a last release? Currently we have way too many alternatives when it comes to testing support and focusing only on one way of doing things certainly helps to reduce the maintenance effort. The next candidate to deprecate would be Testing Tools... Konrad
