[
https://issues.apache.org/jira/browse/LOG4J2-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13657805#comment-13657805
]
Nick Williams commented on LOG4J2-10:
-------------------------------------
I'm okay with using the Maven bundle plugin to create bundles from a single
source. I would strongly oppose any move to split the source into multiple
Maven modules and aggregate the JAR (this would get very ugly quickly; note
that we wouldn't need the shade plugin, the assembly plugin would be
sufficient).
Note that there will also need to be a core-osgi-jpa (or equivalent) bundle.
You did not list that one, and I don't know if it's because you forgot to
mention it or it's missing from your patch. There must be a bundle that pulls
out the dependency on JPA.
> 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: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
