[
https://issues.apache.org/jira/browse/LOG4J2-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13657678#comment-13657678
]
Ralph Goers commented on LOG4J2-10:
-----------------------------------
Thanks for the explanation. I am strongly in favor of this approach but I do
have a question about the names. First, I would prefer that all of these
reside under the "org.apache.logging.log4j.osgi" groupId to separate them from
the non-osgi artifacts, but I'm not sure if that is possible with the maven
bundle plugin. If we do that would the "-osgi-" in the artifact names still be
required? I assume that all of these are still jars so I suppose users might
get confused. In addition, these are all going to appear in the distribution
archive. Ideally they would be separate from the other jars.
I'm going to apply your patch when I can get a chance and I'm sure I will have
more questions.
> 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
