commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Harper (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LANG-749) Incorrect Bundle-SymbolicName in Manifest
Date Tue, 30 Aug 2011 19:49:41 GMT

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

Brandon Harper commented on LANG-749:
-------------------------------------

Figured out how to fix the problem.  All that you need to do is add a property to the pom.xml
to override a default.  See the attached pom.xml.



> Incorrect Bundle-SymbolicName in Manifest
> -----------------------------------------
>
>                 Key: LANG-749
>                 URL: https://issues.apache.org/jira/browse/LANG-749
>             Project: Commons Lang
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 3.0.1
>         Environment: Snow Leopard
>            Reporter: Brandon Harper
>              Labels: build, bundle, jar, manifest, osgi, packaging, symbolicname
>         Attachments: pom.xml
>
>
> The Bundle-SymbolicName in the manifest is:
> Bundle-SymbolicName: org.apache.commons.lang
> It should be:
> Bundle-SymbolicName: org.apache.commons.lang3
> When you install the new lang3 library in an OSGi container such as Apache Felix beside
the old v2.x library, they conflict with each other because the SymbolicName is used as a
unique id and they conflict with each other.  My only work around at the moment is to manually
edit the manifest and repackage.
> TLDR version:  The SymbolicName in the manifest does not reflect the lang3 package structure
and conflicts in OSGi containers which are already using previous versions of Commons Lang.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message