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/05/12 11:41:12 UTC

[jira] [Commented] (SLING-5724) Teleporter: Use o.a.s.testing.clients.osgi.OsgiConsoleClient instead of TeleporterHttpClient

    [ https://issues.apache.org/jira/browse/SLING-5724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15281438#comment-15281438 ] 

Konrad Windszus commented on SLING-5724:
----------------------------------------

That change would also ease implementing SLING-5681.

> Teleporter: Use o.a.s.testing.clients.osgi.OsgiConsoleClient instead of TeleporterHttpClient
> --------------------------------------------------------------------------------------------
>
>                 Key: SLING-5724
>                 URL: https://issues.apache.org/jira/browse/SLING-5724
>             Project: Sling
>          Issue Type: Bug
>          Components: Testing
>    Affects Versions: JUnit Tests Teleporter 1.0.6
>            Reporter: Konrad Windszus
>
> Instead of having another client which deals with installing/uninstalling bundles, the {{ClientSideTeleporter}} should just leverage the class {{org.apache.sling.testing.clients.osgi.OsgiConsoleClient}} for that purpose. That might also help with SLING-5715 as it is using the Apache HTTP Client under the hood, which might be a better choice than just plain HttpUrlConnections which are currently used by {{TeleporterHttpClient}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)