[
https://issues.apache.org/jira/browse/LOGGING-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13585134#comment-13585134
]
Thomas Neidhart commented on LOGGING-124:
-----------------------------------------
Thanks for the clarification, I do not know if changing the packaging will have
an effect on other plugins, so if the osgi metadata is correctly set, I would
prefer to keep it as is for now.
Regarding the symbolic name, I have read the page here:
http://wiki.osgi.org/wiki/Bundle-SymbolicName
The current groupId/artifactId is still commons-logging, but the exported
packages do correspond to org.apache.commons.logging, so I guess we have to
make a choice ;-)
Considering that in the future the groupId will change to org.apache.commons,
it may be better to already use that as the symbolicName?
> Commons logging does not work in an osgi environment
> ----------------------------------------------------
>
> Key: LOGGING-124
> URL: https://issues.apache.org/jira/browse/LOGGING-124
> Project: Commons Logging
> Issue Type: Improvement
> Affects Versions: 1.1.1
> Reporter: Christian Schneider
> Attachments: LOGGING-124.patch
>
>
> Commons logging should provide Manifest information for using it as an OSGI
> bundle. Eventually detection of logging engines and loading of configs should
> also be changed to make commons-logging osgi ready.
> I have given this problem the critical priority as currently many people are
> working on osgi projects and as many open source libs use commons-logging
> this is an important thing to solve.
--
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
