[
https://issues.apache.org/jira/browse/LOG4J2-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13657041#comment-13657041
]
Timothy Ward commented on LOG4J2-10:
------------------------------------
[~garydgregory] [[email protected]] I agree that having to put lots of jars in
your application can be a pain, so I deliberately left the original core jar
alone. This is the one that you would use in Java SE/EE. The smaller OSGi
bundles are typically going to be installed automatically as part of an OSGi
provisioning operation. Having separate modules in OSGi is a nicer way of
building up function without dragging in things you don't need. Another option
is just to mark everything as optional, but this just gives you a "broken out
of the box" scenario, where it looks like the bundle is working, when actually
you really do need some of the dependencies.
> log4j 2.0 should work well with OSGi and Apache Felix
> -----------------------------------------------------
>
> Key: LOG4J2-10
> URL: https://issues.apache.org/jira/browse/LOG4J2-10
> Project: Log4j 2
> Issue Type: Wish
> Reporter: Curt Arnold
> Attachments: reduced-dependency-bundles.patch
>
>
> OSGi and specifically the Apache Felix implementation should be considered
> for framework services such as internal logging and configuration.
> log4j 2.0 should be able to be a provider of OSGi logging services.
> OSGi package visibility declarations should be used to distinguish between
> exported and explicitly supported APIs and implementation specific details.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
