commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Neidhart (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (LOGGING-151) Invalid OSGi bundle id
Date Tue, 09 Apr 2013 08:36:16 GMT

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

Thomas Neidhart edited comment on LOGGING-151 at 4/9/13 8:34 AM:
-----------------------------------------------------------------

The next release will update the groupId to org.apache.commons and we will also update the
symbolic name accordingly.

Edit: prior to the 1.1.2 release the symbolic name was already changed to org.apache.commons.logging,
but was reverted to commons-logging based on a patch from an Apache Felix committer (see LOGGING-124).
                
      was (Author: tn):
    The next release will update the groupId to org.apache.commons and we will also update
the symbolic name accordingly.
                  
> 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

Mime
View raw message