org.eclipse.virgo.kernel.deployer.core.DeploymentException: Dependency satisfaction failed

Spring JIRA | Steve suh | 4 years ago
  1. 0

    It looks like starting with M6a that the the spring oauth 2 bundle cannot be loaded. I verified M6a,b,c, and d error out the with the message below. M6 will load but it is missing certain elements from the latest xsd and well as certain classes that the demo sparklr2 and tonr2 rely on. According to a post on the Virgo forum after asking there about this issue: "It looks like the import of the junit package does not specify resolution:=optional. At least that's the impression I get from the diagnostic "with attributes {optional=true}" since there is no standard attribute or directive named "optional" and the resolution directive is a directive (:=) rather than an attribute (=)." [2012-06-26 17:30:14.378] ERROR fs-watcher org.eclipse.virgo.medic.eventlog.default HD0002E Hot deploy failed for file 'spring-security-oauth2-1.0.0.M6d.jar'. org.eclipse.virgo.kernel.deployer.core.DeploymentException: Dependency satisfaction failed at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.driveInstallPipeline(PipelinedApplicationDeployer.java:363) at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.doInstall(PipelinedApplicationDeployer.java:184) at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.install(PipelinedApplicationDeployer.java:139) at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.deploy(PipelinedApplicationDeployer.java:252) at org.eclipse.virgo.kernel.deployer.hot.HotDeploymentFileSystemListener.deploy(HotDeployerFileSystemListener.java:163) at org.eclipse.virgo.kernel.deployer.hot.HotDeploymentFileSystemListener.onChange(HotDeployerFileSystemListener.java:67) at org.eclipse.virgo.util.io.FileSystemChecker.notifyListeners(FileSystemChecker.java:245) at org.eclipse.virgo.util.io.FileSystemChecker.check(FileSystemChecker.java:166) at org.eclipse.virgo.kernel.deployer.hot.WatchTask.run(WatchTask.java:48) at java.lang.Thread.run(Thread.java:662) Caused by: org.eclipse.virgo.kernel.osgi.framework.UnableToSatisfyBundleDependenciesException: Unable to satisfy dependencies of bundle 'org.springframework.security.oauth' at version '1.0.0.M6d': Cannot resolve: org.springframework.security.oauth Resolver report: An Import-Package could not be resolved. Resolver error data <Import-Package: org.junit.internal; version="[4.8.2,5.0.0)">. Caused by missing constraint in bundle <org.springframework.security.oauth_1.0.0.M6d> constraint: <Import-Package: org.junit.internal; version="[4.8.2,5.0.0)"> with attributes {optional=true} 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)

    Spring JIRA | 4 years ago | Steve suh
    org.eclipse.virgo.kernel.deployer.core.DeploymentException: Dependency satisfaction failed
  2. 0

    It looks like starting with M6a that the the spring oauth 2 bundle cannot be loaded. I verified M6a,b,c, and d error out the with the message below. M6 will load but it is missing certain elements from the latest xsd and well as certain classes that the demo sparklr2 and tonr2 rely on. According to a post on the Virgo forum after asking there about this issue: "It looks like the import of the junit package does not specify resolution:=optional. At least that's the impression I get from the diagnostic "with attributes {optional=true}" since there is no standard attribute or directive named "optional" and the resolution directive is a directive (:=) rather than an attribute (=)." [2012-06-26 17:30:14.378] ERROR fs-watcher org.eclipse.virgo.medic.eventlog.default HD0002E Hot deploy failed for file 'spring-security-oauth2-1.0.0.M6d.jar'. org.eclipse.virgo.kernel.deployer.core.DeploymentException: Dependency satisfaction failed at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.driveInstallPipeline(PipelinedApplicationDeployer.java:363) at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.doInstall(PipelinedApplicationDeployer.java:184) at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.install(PipelinedApplicationDeployer.java:139) at org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.deploy(PipelinedApplicationDeployer.java:252) at org.eclipse.virgo.kernel.deployer.hot.HotDeploymentFileSystemListener.deploy(HotDeployerFileSystemListener.java:163) at org.eclipse.virgo.kernel.deployer.hot.HotDeploymentFileSystemListener.onChange(HotDeployerFileSystemListener.java:67) at org.eclipse.virgo.util.io.FileSystemChecker.notifyListeners(FileSystemChecker.java:245) at org.eclipse.virgo.util.io.FileSystemChecker.check(FileSystemChecker.java:166) at org.eclipse.virgo.kernel.deployer.hot.WatchTask.run(WatchTask.java:48) at java.lang.Thread.run(Thread.java:662) Caused by: org.eclipse.virgo.kernel.osgi.framework.UnableToSatisfyBundleDependenciesException: Unable to satisfy dependencies of bundle 'org.springframework.security.oauth' at version '1.0.0.M6d': Cannot resolve: org.springframework.security.oauth Resolver report: An Import-Package could not be resolved. Resolver error data <Import-Package: org.junit.internal; version="[4.8.2,5.0.0)">. Caused by missing constraint in bundle <org.springframework.security.oauth_1.0.0.M6d> constraint: <Import-Package: org.junit.internal; version="[4.8.2,5.0.0)"> with attributes {optional=true} 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)

    Spring JIRA | 4 years ago | Steve suh
    org.eclipse.virgo.kernel.deployer.core.DeploymentException: Dependency satisfaction failed
  3. 0

    db:: 4.09::Unknown server version 3d

    hivmr.com | 7 months ago
    org.eclipse.virgo.kernel.deployer.core.DeploymentException: Dependency satisfaction failed
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    db:: 3.60::Security question: unknown tcp connection pk

    hivmr.com | 7 months ago
    org.eclipse.virgo.kernel.deployer.core.DeploymentException: Dependency satisfaction failed
  6. 0

    Unable to refer vijava jar file in Virgo Server

    Stack Overflow | 2 years ago | Selvaraj
    org.eclipse.virgo.kernel.osgi.framework.UnableToSatisfyBundleDependenciesException: Unable to satisfy dependencies of bundle 'com.acme.selvaService.SelvaService' at version '1.0.0': Cannot resolve: com.acme.selvaService.SelvaService Resolver report: An Import-Package could not be resolved. Resolver error data . Caused by missing constraint in bundle constraint: </p> <pre><code>at org.eclipse.virgo.kernel.install.pipeline.stage.resolve.internal.QuasiResolveStage.process(QuasiResolveStage.java:46)

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. org.eclipse.virgo.kernel.osgi.framework.UnableToSatisfyBundleDependenciesException

      Unable to satisfy dependencies of bundle 'org.springframework.security.oauth' at version '1.0.0.M6d': Cannot resolve: org.springframework.security.oauth Resolver report: An Import-Package could not be resolved. Resolver error data <Import-Package: org.junit.internal; version="[4.8.2,5.0.0)">. Caused by missing constraint in bundle <org.springframework.security.oauth_1.0.0.M6d> constraint: <Import-Package: org.junit.internal; version="[4.8.2,5.0.0)"> with attributes {optional=true}

      at org.eclipse.virgo.kernel.install.pipeline.stage.resolve.internal.QuasiResolveStage.process()
    2. org.eclipse.virgo
      PipelinedApplicationDeployer.driveInstallPipeline
      1. org.eclipse.virgo.kernel.install.pipeline.stage.resolve.internal.QuasiResolveStage.process(QuasiResolveStage.java:46)
      2. org.eclipse.virgo.kernel.install.pipeline.internal.StandardPipeline.doProcessGraph(StandardPipeline.java:62)
      3. org.eclipse.virgo.kernel.install.pipeline.internal.CompensatingPipeline.doProcessGraph(CompensatingPipeline.java:73)
      4. org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipelineStage.process(AbstractPipelineStage.java:41)
      5. org.eclipse.virgo.kernel.install.pipeline.internal.StandardPipeline.doProcessGraph(StandardPipeline.java:62)
      6. org.eclipse.virgo.kernel.install.pipeline.stage.AbstractPipelineStage.process(AbstractPipelineStage.java:41)
      7. org.eclipse.virgo.kernel.deployer.core.internal.PipelinedApplicationDeployer.driveInstallPipeline(PipelinedApplicationDeployer.java:360)
      7 frames