[
https://issues.apache.org/jira/browse/SLING-6551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-6551:
-----------------------------------
Fix Version/s: JUnit Tests Teleporter 1.0.12
> Allow to embed a complete classes directory in the test bundle
> --------------------------------------------------------------
>
> Key: SLING-6551
> URL: https://issues.apache.org/jira/browse/SLING-6551
> Project: Sling
> Issue Type: Improvement
> Components: Apache Sling Testing Rules
> Affects Versions: JUnit Tests Teleporter 1.0.10
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Fix For: JUnit Tests Teleporter 1.0.12
>
>
> Currently only
> # directly referenced dependencies from the IT can be automatically be
> embedded (by whitelisting the package prefixes via
> {{ClientSideTeleporter.includeDependencyPrefix(...)}}
> # invididual fully-qualified classes can be embedded manually as well via
> {{ClientSideTeleporter.embedClass(...)}}
> This is not enough in case the teleporter-based IT is part of the bundle
> which is supposed to be tested. The mechanism in 1) will not detect any
> implementation classes like OSGi services (because the IT itself only
> references the according interface). The mechanism 2) causes a lot of effort
> as each class name needs to be given separately. In this case it would be
> best to be able to include a full directory containing java classes in the
> testing bundle.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
