[
https://issues.apache.org/jira/browse/LOG4J2-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713632#comment-13713632
]
Timothy Ward commented on LOG4J2-10:
------------------------------------
Hi Nick,
You definitely want to declare the import for the servlet package so that web
bundles can use log4j without having to put it in WEB-INF/lib. This means that
you also need to export the o.a.l.l.core.web package (so that web bundles can
import it and use it). The maven bundle plugin will calculate your uses
constraint to make sure this all works properly.
If o.a.l.l.core.web works with Servlet 2.5, then the OSGi packaging should use
servlet 2.5 on the build path to pick up the right import version range. This
should be "[2.5,3)" because servlet 3 has a semantic version of 2.6 :)
>From your description of how things are laid out I don't forsee any problems
>in OSGi, assuming that the Import-Package version range is set properly.
Tim
> 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]
