【问题标题】:OSGI: Import-Package could not be resolvedOSGI:导入包无法解析
【发布时间】:2012-10-11 03:35:35
【问题描述】:

我正在尝试将捆绑包部署到 osgi,但出现此错误

An Import-Package could not be resolved. Resolver error data <Import-Package: signature; version="0.0.0">. Caused by missing constraint in bundle....
constraint: <Import-Package: signature; version="0.0.0">

at org.eclipse.virgo.kernel.install.pipeline.stage.resolve.internal.QuasiResolveStage.process(QuasiResolveStage.java:46)
at org.eclipse.virgo.kernel.install.pipeline.internal.StandardPipeline.doProcessGraph(StandardPipeline.java:62)
at org.eclipse.virgo.kernel.install.pipeline.internal.CompensatingPipeline.doProcessGraph(CompensatingPipeline.java:73)
at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipelineStage.process(AbstractPipelineStage.java:41)
at org.eclipse.virgo.kernel.install.pipeline.internal.StandardPipeline.doProcessGraph(StandardPipeline.java:62)
at org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipelineStage.process(AbstractPipelineStage.java:41)
at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.driveInstallPipeline(PipelinedApplicationDeployer.java:360)
... 9 common frames omitted

我在 maven 的任何地方都找不到这个签名依赖,因为我的其他依赖问题有完整的组路径,我假设这个工件只被称为“签名”。我遇到的与此类似的其他问题是 jline 和 jess,但在查找这些工件时没有问题。

有人知道这个神器吗?

谢谢!

【问题讨论】:

    标签: maven import dependencies osgi package


    【解决方案1】:

    你是否在蓝图中用这个包名定义了一个类?蓝图上下文也由 maven bundle 插件分析。

    【讨论】:

      猜你喜欢
      • 2017-05-12
      • 2012-04-04
      • 2012-12-06
      • 1970-01-01
      • 2018-12-28
      • 1970-01-01
      • 2020-04-21
      • 2021-06-27
      • 2015-07-04
      相关资源
      最近更新 更多