[
https://issues.apache.org/jira/browse/LOG4J2-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13657049#comment-13657049
]
Gary Gregory commented on LOG4J2-10:
------------------------------------
I do not see one solution better than the other: As it is now, I have to
manually add a jar for JDBC or JMS, for example: the API jar, Core jar and a
JMS provider jar(s) (or a JDBC driver jar(s)). How is having a bunch of little
bundles solve this? I still have to manually add jars or bundles for JDBC
drivers and JMS providers. The JDBC API is included in the JRE but JMS is not.
So even if I have a log4j-jms bundle that drags in the JMS API, that does not
help me bring in the JMS provider I want. So the problem cannot be 100% solved
with bundles.
I've never had a Log4J 1 and 2 scenario that did not require fiddling with the
classpath, using bundles is not going to change that.
We should mark our current jars with OSGi optional settings in all the right
places, that's a given IMO.
> 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]
