commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Neidhart (JIRA)" <>
Subject [jira] [Commented] (LOGGING-151) Invalid bundle id
Date Tue, 09 Apr 2013 07:38:15 GMT


Thomas Neidhart commented on LOGGING-151:

The same page also states:

If automatically generated via Maven Bundle Plugin, takes the form ${pom.groupId}.${pom.artifactId},
or ${pom.artifactId} if it already starts with ${pom.groupId}. 

and this is what has been used as the groupId/artifactId is still commons-logging.
> 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