[
https://issues.apache.org/jira/browse/LOGGING-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13626393#comment-13626393
]
Emmanuel Bourg commented on LOGGING-151:
----------------------------------------
If the next release has a new groupId that means it will be binary incompatible
and live in a different package. That leaves the 1.1.x line with broken OSGi
metadata forever.
> Invalid OSGi bundle id
> ----------------------
>
> Key: LOGGING-151
> URL: https://issues.apache.org/jira/browse/LOGGING-151
> Project: Commons Logging
> Issue Type: Bug
> Affects Versions: 1.1.2
> Reporter: Krzysztof Daniel
>
> Version 1.1.2 got a Manifest.mf that supports OSGi. Unfortunately, the bundle
> id specified there is incorrect. According to
> http://wiki.osgi.org/wiki/Bundle-SymbolicName "A BSN often takes the form of
> a reverse domain name. " So the proper and expected name would be
> org.apache.commons.logging .
--
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
