You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2014/01/21 15:13:26 UTC
[jira] [Updated] (SLING-3328) Simplify SlingTestBase usage with an
already running instance
[ https://issues.apache.org/jira/browse/SLING-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bertrand Delacretaz updated SLING-3328:
---------------------------------------
Summary: Simplify SlingTestBase usage with an already running instance (was: Simplify using SlingTestBase with an already running instance)
> Simplify SlingTestBase usage with an already running instance
> -------------------------------------------------------------
>
> Key: SLING-3328
> URL: https://issues.apache.org/jira/browse/SLING-3328
> Project: Sling
> Issue Type: Improvement
> Components: Testing
> Reporter: Jörg Hoh
> Assignee: Bertrand Delacretaz
> Priority: Minor
> Fix For: org.apache.sling.testing.tools 1.0.8
>
> Attachments: standalone-sling-instance.patch
>
>
> In the current 1.0.7-SNAPSHOT release you need to provide these system properties to make the testing tools connect to run against an already running Sling instance:
> * test.server.url
> * jar.executor.jar.name.regexp
> * jar.executor.jar.folder
> Only the first one is really needed, the 2 others are only required to make the creation of the JarExecutor succesfull. If you want to connect only to an instance which is already running, the JarExecutor is not needed at all.
> Therefor I would like to get rid of the need to specify the 2 "jar.executor.*" properties. Please see attached patch for a proposal how to achieve it.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)