片段的约束与主机冲突

Question

我正在尝试使用Fragment-Host从bundle B扩展bundle A的导入.在BI中有这一行:Fragment-Host:在bundle B的Import-Package中我添加了bundle A所需的导入

当我尝试使用清单更新bundle B并启动它时,我收到错误:"片段与主机冲突的约束",包含B中存在的所有导入列表但是在检查包AI的清单时如果这些进口不存在,那么为什么这些进口应该发生冲突

另外值得一提的是,我只在OSGi容器中运行了两个捆绑包的一个版本,并且我已经尝试在更新后重新启动容器.

捆绑一个清单:

Manifest-Version: 1.0
Archiver-Version: Plexus Archiver
Created-By: Apache Maven
Built-By: hudson
Build-Jdk: 1.6.0_20
Export-Package: <list of packages>
Tool: Bnd-0.0.311
Bundle-Name: Logging infrastructure
Bundle-RequiredExecutionEnvironment: JavaSE-1.6
Bundle-Version: 0.7.0
Bundle-ManifestVersion: 2
Bundle-Activator: <activator class>
Bundle-SymbolicName: com.mycomp.bundlea
Import-Package: com.sap.tc.logging,org.apache.commons.logging,org.apac
 he.log4j,org.apache.log4j.helpers,org.apache.log4j.spi,org.apache.log
 4j.xml,org.eclipse.osgi.framework.console;version="1.0",org.osgi.fram
 ework;version="1.5",org.osgi.service.cm;version="1.2",org.osgi.servic
 e.log;version="1.3",org.osgi.util.tracker;version="1.4"
Eclipse-RegisterBuddy: com.sap.org.apache.log4j

捆绑B清单:

    Manifest-Version: 1.0
Export-Package: org.perf4j;uses:="org.perf4j.chart,org.perf4j.helpers"
 ,org.perf4j.aop;uses:="javax.interceptor,org.apache.commons.jexl,org.
 aspectj.lang,org.aspectj.lang.annotation,org.perf4j",org.perf4j.chart
 ;uses:="org.perf4j,org.perf4j.helpers",org.perf4j.commonslog;uses:="o
 rg.apache.commons.logging,org.perf4j",org.perf4j.commonslog.aop;uses:
 ="org.aspectj.lang.annotation,org.perf4j,org.perf4j.aop,org.perf4j.co
 mmonslog",org.perf4j.helpers;uses:="javax.management,org.perf4j",org.
 perf4j.javalog;uses:="org.perf4j",org.perf4j.javalog.aop;uses:="org.a
 spectj.lang.annotation,org.perf4j,org.perf4j.aop,org.perf4j.javalog",
 org.perf4j.log4j;uses:="javax.management,org.apache.log4j,org.apache.
 log4j.helpers,org.apache.log4j.spi,org.perf4j,org.perf4j.chart,org.pe
 rf4j.helpers",org.perf4j.log4j.aop;uses:="org.aspectj.lang.annotation
 ,org.perf4j,org.perf4j.aop,org.perf4j.log4j",org.perf4j.log4j.servlet
 ;uses:="org.perf4j.chart,org.perf4j.servlet",org.perf4j.servlet;uses:
 ="javax.servlet,javax.servlet.http,org.perf4j.chart",org.perf4j.slf4j
 ;uses:="org.perf4j,org.slf4j",org.perf4j.slf4j.aop;uses:="org.aspectj
 .lang.annotation,org.perf4j,org.perf4j.aop,org.perf4j.slf4j"
Implementation-Title: Perf4J
Implementation-Version: 0.9.13
Built-By: devinea
Specification-Vendor: perf4j.org
Tool: Bundlor 1.0.0.RELEASE
Created-By: Apache Maven
Implementation-Vendor: perf4j.org
Implementation-Vendor-Id: org.perf4j
Build-Jdk: 1.5.0_22
Specification-Title: Perf4J
Import-Package: javax.interceptor,javax.management,javax.servlet,javax
 .servlet.http,org.apache.commons.jexl,org.apache.commons.jexl.context
 ,org.apache.commons.logging,org.apache.log4j,org.apache.log4j.helpers
 ,org.apache.log4j.spi,org.aspectj.lang,org.aspectj.lang.annotation,or
 g.slf4j,org.perf4j.log4j
Specification-Version: 0.9.13
Main-Class: org.perf4j.LogParser
Archiver-Version: Plexus Archiver
Bundle-SymbolicName: org.codehaus.perf4j
Bundle-Version: 0.9.13
Fragment-Host: com.mycomp.bundlea

有任何想法吗...？

Answer 1

约束冲突很难远程诊断,特别是因为Equinox在其错误消息中提供的信息非常少...... Felix在这方面做得更好但看起来你与Equinox绑定了一些特定于Eclipse的扩展头.

有关一些常规指针和问题的解释,请参阅我之前写的以下两篇博文:

http://njbartlett.name/2011/09/02/uses-constraints.html

http://njbartlett.name/2011/03/31/uses-constraints-in-felix.html