You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Matt Sicker (Jira)" <ji...@apache.org> on 2023/12/01 23:43:00 UTC
[jira] [Resolved] (LOG4J2-516) As a developer using OSGi, I want to use Log4J as my OSGi Log Service
[ https://issues.apache.org/jira/browse/LOG4J2-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Sicker resolved LOG4J2-516.
--------------------------------
Resolution: Won't Fix
For OSGi purposes, we've decided to delegate this responsibility to Pax-Logging which makes customizations on top of Log4j.
> As a developer using OSGi, I want to use Log4J as my OSGi Log Service
> ---------------------------------------------------------------------
>
> Key: LOG4J2-516
> URL: https://issues.apache.org/jira/browse/LOG4J2-516
> Project: Log4j 2
> Issue Type: Story
> Components: Core
> Environment: Felix, Equinox, OSGi
> Reporter: Matt Sicker
> Priority: Major
> Labels: osgi
>
> See [the javadocs|http://www.osgi.org/javadoc/r5/cmpn/org/osgi/service/log/package-summary.html] for some details. I'd like to be able to import the log service bundle and be able to use Log4J as the backend if it has been registered in OSGi.
> This would require a module that adapts the logging infrastructure to OSGi's logging service. I think that would be a good addition to the bundles exported.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)