[
https://issues.apache.org/jira/browse/SLING-5401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069522#comment-15069522
]
Bertrand Delacretaz commented on SLING-5401:
--------------------------------------------
AFAICS all the {{Import-Package ch.qos.logback.*}} statements of the junit.core
bundle (in trunk) have {{resolution:=optional}}, so the bundle should start
even if those packages are not available.
The {{TestLogServlet}} should just be unavailable in such a case - I haven't
tested that though.
Did I miss something, or is something else getting in your way with Karaf?
> JUnit Core has hard dependency on Logback
> -----------------------------------------
>
> Key: SLING-5401
> URL: https://issues.apache.org/jira/browse/SLING-5401
> Project: Sling
> Issue Type: Bug
> Components: Testing
> Affects Versions: JUnit Core 1.0.12, JUnit Core 1.0.14
> Reporter: Oliver Lietz
>
> While investigating why [running launchpad integration tests against Sling on
> Karaf|SLING-3821] suddenly completely fail I found that JUnit Core has now a
> hard dependency on Logback because of {{TestLogServlet}}.
> That means if your system under test does not use Logback as backend testing
> is not possible at all. That should be documented at least at [JUnit
> server-side testing support
> bundles|https://sling.apache.org/documentation/bundles/org-apache-sling-junit-bundles.html].
> [~chetanm], [~bdelacretaz]: Is that hard dependency really desired?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
