[
https://issues.apache.org/jira/browse/LOG4J2-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13657029#comment-13657029
]
Timothy Ward commented on LOG4J2-10:
------------------------------------
[[email protected]] some of the things being proposed in [LOG4J2-238]
are probably reasonable, although optional imports in OSGi are hard to get
right (i.e. avoid NoClassDefFoundError problems). The patch looks as though
it's moving in the right direction for better OSGi support, services are a much
better mechanism for sharing objects than using fragments and static factories.
There might be a slightly better approach for structuring the service
plug-point so that it's less invasive to the non-OSGi users. I can take a
closer look over the next week or so.
I've attached a bare-bones patch for creating scoped fragments (the minimal
change I could see) that should allow OSGi clients to only install the parts of
core that they need in a safe way.
> 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]
