Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Tue, 9 Apr 2013 07:38:15 +0000 (UTC)
From: "Thomas Neidhart (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.12641526.1365489111673.133612.1365493095969@arcas>
In-Reply-To: <JIRA.12641526.1365489111673@arcas>
References: <JIRA.12641526.1365489111673@arcas>
Subject: [jira] [Commented] (LOGGING-151) Invalid bundle id
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/LOGGING-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13626356#comment-13626356 ] 

Thomas Neidhart commented on LOGGING-151:
-----------------------------------------

The same page also states:

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

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