Apache Felix obr 部署错误消息
obr部署命令失败时如何读取错误消息？ 这是一个例子：
-> obr deploy configuration-exporter
Unsatisfied requirement(s):
---------------------------
(&(package=com.google.common.collect))
RoutingService :: DAO
(&(package=com.sybase365.routingservice))
ARF :: Service Bundle :: Configuration Exporter
(&(package=com.google.common.base))
RoutingService :: DAO
(service=org.osgi.service.event.EventHandler)
Apache Felix EventAdmin
(&(package=com.google.common.base))
ARF :: Service Bundle :: Configuration Exporter
(|(ee=J2SE-1.5))
Guava: Google Core Libraries for Java 1.5
(&(package=com.google.common.collect))
ARF :: Service Bundle :: Configuration Exporter
(service=org.osgi.service.event.EventHandler)
Apache Felix EventAdmin
如何阅读上面的消息？其实还有什么不满足的呢？
How to read error messages when obr deploy command fails?
Here is an example:
-> obr deploy configuration-exporter
Unsatisfied requirement(s):
---------------------------
(&(package=com.google.common.collect))
RoutingService :: DAO
(&(package=com.sybase365.routingservice))
ARF :: Service Bundle :: Configuration Exporter
(&(package=com.google.common.base))
RoutingService :: DAO
(service=org.osgi.service.event.EventHandler)
Apache Felix EventAdmin
(&(package=com.google.common.base))
ARF :: Service Bundle :: Configuration Exporter
(|(ee=J2SE-1.5))
Guava: Google Core Libraries for Java 1.5
(&(package=com.google.common.collect))
ARF :: Service Bundle :: Configuration Exporter
(service=org.osgi.service.event.EventHandler)
Apache Felix EventAdmin
How to read the above message? What is actually unsatisfied?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我假设您的 obr 缺少软件包：
然后您可能没有运行某些服务：
并且您可能没有所需的 java 运行时：
我通常采用第一个丢失的软件包 - 并尝试解决它。如果它消除了这个错误，我就会继续下去。如果没有 - 那么你的 osgi 运行时有问题。也许您缺少一些部署所需的捆绑包？
I assume that your obr is missing packages:
and then you probably don't have some services running:
and you probably don't have the required java-runtime:
I usually take the first missing package - and try to resolve it. If it gets rid of that error, I keep going. If not - then something is wrong with your osgi runtime. Perhaps your are missing some bundles that it needs in order to do the deploy?