[
https://issues.apache.org/jira/browse/LOG4J2-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15720658#comment-15720658
]
Ludovic HOCHET commented on LOG4J2-1664:
----------------------------------------
There is more to do:
_ move the remainder of preexisting OSGi tests to the log4j-osgi module, that
is port api
org.apache.logging.log4j.osgi.AbstractLoadBundleTest::testLoadStartStop and add
a test for log4j-1.2-api which require special handling since it is a fragment
to core.
_ evaluate the output when clean installing just the log4j-osgi module ("Cannot
cast org.apache.logging.log4j.core.osgi.BundleContextSelector to
org.apache.logging.log4j.core.selector.ContextSelector" and "DEBUG: Bundle
org.apache.logging.log4j.core [2] log4j2-test7e809b79.properties not found by
org.apache.logging.log4j.core [2]" and related), these don't change the result
of the existing tests since they test OSGi parts, but may indicate potential
issues in the Log4J side.
> Improve OSGi unit tests
> -----------------------
>
> Key: LOG4J2-1664
> URL: https://issues.apache.org/jira/browse/LOG4J2-1664
> Project: Log4j 2
> Issue Type: Improvement
> Components: API, Core
> Affects Versions: 2.7
> Reporter: Ludovic HOCHET
> Fix For: 2.8
>
> Attachments: patch-log4j2-1664-2.diff
>
>
> Following up on LOG4J2-1637, this ticket is to improve the OSGi unit tests.
> Ideally they should catch issues like LOG4J2-1637, but other improvements are
> welcome too.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
