[ 
https://issues.apache.org/jira/browse/SHIRO-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francois Papon resolved SHIRO-626.
----------------------------------
    Resolution: Resolved

> Bundle symbolic name conflict
> -----------------------------
>
>                 Key: SHIRO-626
>                 URL: https://issues.apache.org/jira/browse/SHIRO-626
>             Project: Shiro
>          Issue Type: Bug
>            Reporter: Rakesh Kumar
>            Assignee: Francois Papon
>            Priority: Major
>              Labels: OSGi
>             Fix For: 1.4.1
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Hi,
> I was trying to use Apache Shiro in OSGi environment but getting exception 
> while installing shiro-config-* bundles.
> Bundle symbolic name for these bundles is same which results in exception 
> being thrown at deployment time.
> Here are the conflicting bundles
> 1. shiro-config-ogdl - declares the below given header in pom
>  <Bundle-SymbolicName>org.apache.shiro.config.core</Bundle-SymbolicName>
> 2. shiro-config-core - Also declares the below given header in pom
>  <Bundle-SymbolicName>org.apache.shiro.config.core</Bundle-SymbolicName>
> Exception trace:
> org.osgi.framework.BundleException: Bundle symbolic name and version are not 
> unique: org.apache.shiro.config.core:1.4.0
>       at 
> org.apache.felix.framework.BundleImpl.createRevision(BundleImpl.java:1344)
>       at org.apache.felix.framework.BundleImpl.<init>(BundleImpl.java:113)
>       at org.apache.felix.framework.Felix.installBundle(Felix.java:3026)
>       at 
> org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:167)
>       at 
> org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:140)
> Ideally the symbolic names should be unique. I can still live with disabling 
> this check using "org.osgi.framework.bsnversion=multiple" but that is not 
> appropriate.
> Please let me know if more information is needed.
> Thanks,
> Rakesh



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to