[
https://issues.apache.org/jira/browse/LOG4J2-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713690#comment-13713690
]
Nick Williams commented on LOG4J2-10:
-------------------------------------
So, OSGi already sounds far more complicated than anything I will ever want to
use. I'm starting to think of "DLL Hell." Regular JAR stuff "just works."
So o.a.l.l.core.web works with Servlet 2.5, 3.0, 3.1, etc. So it needs to be
"2.5+" however that works.
Log4j would normally go in /WEB-INF/lib. It wouldn't normally go in the
container unless the container is actually using Log4j. Even then, Log4j could
still go in /WEB-INF/lib. But I don't understand any of this.
Everything you just said is complete gibberish to me, so somebody else is going
to have to make whatever changes need making.
Nick
> 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-2.patch,
> 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: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
