[
https://issues.apache.org/jira/browse/LOG4J2-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13656200#comment-13656200
]
Timothy Ward commented on LOG4J2-10:
------------------------------------
[~rem...@yahoo.com]
The simplest way I can think of to achieve #3 would be to split log4j-core into
multiple bundles. A "main" bundle containing most of the log4j-core, and then
some small extensions for each of the optional pieces. At a glance I would
expect there to be an extension for "async", one for JPA, and two NoSQL (one
for mongo and one for couch), but there may be others that could be easily
extracted to reduce the number of package imports needed. I did wonder whether
the jackson dependencies could be easily factored out, but it's not as easy as
separating the JPA, disruptor, mongo and couch dependencies.
OSGi clients have to be explicit about the parts of log4j that they use, so it
will be easy to identify the pieces of log4j that need to be installed for a
particular client to work, without having to pull in the dependencies for the
whole thing.
You could always use the maven shade plugin to aggregate the individual pieces
back into a single JAR for use in Java SE/EE deployments.
> 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
>
> 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: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
