Krzysztof Daniel commented on LOGGING-151:
Yes, I'm aware of that. I'd question the existing groupId/artifactId, too, if only had not it been used for such a long time in its current form.
The same wiki page provides an example which is in the form of a reverse domain name notation. Also, commons-logging is a widely distributed as an OSGI bundle in Eclipse, which wraps it as org.apache.commons.logging (according to http://wiki.eclipse.org/index.php/Naming_Conventions).
This is of course a very drastic change to the whole community, and I don't want to insist on it (although it would be nice).
I'm, however, using this package in Fedora, and it has been osgified there, and in Eclipse, for a long time, with org.apache.commons.logging id. Current name (commons-logging) is a breaker for me, and I'll have to patch it otherwise.
> Invalid 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