commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Krzysztof Daniel (JIRA)" <>
Subject [jira] [Commented] (LOGGING-151) Invalid bundle id
Date Tue, 09 Apr 2013 08:20:16 GMT


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

Maven conventions ( suggest
groupId on a project level (org.apache.commons is listed as an example), so a natural consequence
would be naming a jar logging.jar and getting ${pom.groupId}.${pom.artifactId} resolved to

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:
>             Project: Commons Logging
>          Issue Type: Bug
>    Affects Versions: 1.1.2
>            Reporter: Krzysztof Daniel
> Version 1.1.2 got a that supports OSGi. Unfortunately, the bundle id specified
there is incorrect. According to "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:

View raw message