[
https://issues.apache.org/jira/browse/LOG4J2-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713804#comment-13713804
]
Pedro Lamarão commented on LOG4J2-10:
-------------------------------------
Regular JAR stuff doesn't just work.
It leads to "JAR hell".
You won't see "JAR Hell" between two servlet modules because they live not
under regular JAR rules, they live under J2EE module isolation rules.
In particular, servlet modules have this WEB-INF/lib trick where every
dependency is "private".
This is equivalent to the solution Microsoft gave to "DLL Hell" -- currently
named "private assemblies".
Of course, in practice, everything in a servlet container ends up being
"private" somehow.
"shared" just doensn't work.
Because "shared" leads to "JAR Hell".
The frustration caused by OSGi's strictness is understandable.
But OSGi is a solution to a true problem -- which you may or may not have.
I know I do.
> 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: [email protected]
For additional commands, e-mail: [email protected]
