Quantcast
Channel: VMware Communities : Discussion List - vSphere Client SDK
Viewing all articles
Browse latest Browse all 2218

"Resolver reported uses conflict for import" on vcenter 6.0 update 2

$
0
0

We were testing out extension that works fine with vcenter 5.5 and 6.0 update 1 and the vcenter 6.0 update 2 and noticed the following issue. Its hard to tell what is going on.

 

 

[2016-03-16T14:20:43.895-07:00] [ERROR] fs-watcher                    org.eclipse.virgo.medic.eventlog.default                         DE0002E Installation of bundle 'com.mycompany.service' version '4.0.0' failed. org.eclipse.vir
go.kernel.osgi.framework.UnableToSatisfyBundleDependenciesException: Unable to satisfy dependencies of bundle 'com.mycompany.service' at version '4.0.0': Cannot resolve: com.mycompany.service    Resolver report:        Uses violation: <Import-Package: com.vmware.vise.data.uri; version="0.0.0"> in bundle <com.mycompany.service_4.0.0[1458163243648]>             Resolver reported uses conflict for import        Uses violation: <Import-Package: com.vmware.vise.data.query; version="0.0.0"> in bundle <com.mycompany.service_4.0.0[1458163243648]>             Resolver reported uses conflict for import        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:359)        at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.doInstall(PipelinedApplicationDeployer.java:185)        at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.install(PipelinedApplicationDeployer.java:140)        at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.deploy(PipelinedApplicationDeployer.java:253)        at org.eclipse.virgo.nano.deployer.hot.HotDeploymentFileSystemListener.deploy(HotDeployerFileSystemListener.java:225)        at org.eclipse.virgo.nano.deployer.hot.HotDeploymentFileSystemListener.onChange(HotDeployerFileSystemListener.java:79)        at org.eclipse.virgo.util.io.FileSystemChecker.notifyListeners(FileSystemChecker.java:380)        at org.eclipse.virgo.util.io.FileSystemChecker.check(FileSystemChecker.java:289)        at org.eclipse.virgo.nano.deployer.hot.WatchTask.run(WatchTask.java:49)        at java.lang.Thread.run(Unknown Source)

Viewing all articles
Browse latest Browse all 2218

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>