[
https://issues.apache.org/jira/browse/LOG4J2-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Ward updated LOG4J2-10:
-------------------------------
Attachment: reduced-dependency-bundles-2.patch
A couple of things were pointed out:
1. It would be better if the additional artifacts added osgi to their groupId -
this is changed (and easy to change back)
2. The first patch missed creating a core-osgi-jpa bundle - this is fixed
Currently the core-osgi-reduced bundle has external dependencies on
com.lmax.disruptor.util and a couple of Jackson packages. Removing these
dependencies will require code changes (either to remove the dependency, or to
push it into a package that can be extracted into a separate bundle)
The symbolic names of these bundles are still
${project.parent.groupId}.${project.artifactId} which means they are currently
of the form:
o.a.l.log4j-core-osgi-XXXX
This is easy to change, but care should be taken to avoid clashes as OSGi uses
symbolic name and version as a unique identifier for the bundle.
> 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]
