Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-6672

Cannot install SY bundles from Integration Pack into 6.3.0.R2

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Critical Critical
    • None
    • jboss-fuse-6.3, fuse-6.x-GA
    • Integration Pack, SwitchYard
    • None
    • % %
    • Hide

      1. Configure Fuse according to steps described at IntegrationPack
      2. features:install fuse-bxms-switchyard-bpm
      3. features:install fuse-bxms-switchyard-rules
      4. if you don't see the error then shutdown the fuse and start it again

      Show
      1. Configure Fuse according to steps described at IntegrationPack 2. features:install fuse-bxms-switchyard-bpm 3. features:install fuse-bxms-switchyard-rules 4. if you don't see the error then shutdown the fuse and start it again

      I cannot install Integration Pack into Fuse on Karaf 6.3.0.R2 (build 251 or 253). I'm still getting the following error

      Error executing command: Could not start bundle mvn:org.jboss.integration.fuse/switchyard-component-common-knowledge/1.7.0.redhat-630019 in feature(s) fuse-bxms-switchyard-common-knowledge-1.7.0.redhat-630019: Uses constraint violation. Unable to resolve bundle revision org.jboss.integration.fuse.switchyard-component-common-knowledge [420.0] because it is exposed to package 'org.jboss.logging' from bundle revisions org.ops4j.pax.logging.pax-logging-api [7.0] and org.jboss.logging.jboss-logging [326.0] via two dependency chains.

Chain 1:
  org.jboss.integration.fuse.switchyard-component-common-knowledge [420.0]
    import: (&(osgi.wiring.package=org.jboss.logging)(version>=3.1.0)(!(version>=4.0.0)))
     |
    export: osgi.wiring.package=org.jboss.logging
  org.ops4j.pax.logging.pax-logging-api [7.0]

Chain 2:
  org.jboss.integration.fuse.switchyard-component-common-knowledge [420.0]
    import: (&(osgi.wiring.package=org.switchyard.config.model.composite.v1)(version>=2.0.0)(!(version>=3.0.0)))
     |
    export: osgi.wiring.package=org.switchyard.config.model.composite.v1; uses:=org.jboss.logging
  org.switchyard.switchyard-config [353.0]
    import: (&(osgi.wiring.package=org.jboss.logging)(version>=3.1.0)(!(version>=4.0.0)))
     |
    export: osgi.wiring.package=org.jboss.logging
  org.jboss.logging.jboss-logging [326.0]
[ERROR] Error executing command: Could not start bundle mvn:org.jboss.integration.fuse/switchyard-component-common-knowledge/1.7.0.redhat-630019 in feature(s) fuse-bxms-switchyard-common-knowledge-1.7.0.redhat-630019: Uses constraint violation. Unable to resolve bundle revision org.jboss.integration.fuse.switchyard-component-common-knowledge [420.0] because it is exposed to package 'org.jboss.logging' from bundle revisions org.ops4j.pax.logging.pax-logging-api [7.0] and org.jboss.logging.jboss-logging [326.0] via two dependency chains.

Chain 1:
  org.jboss.integration.fuse.switchyard-component-common-knowledge [420.0]
    import: (&(osgi.wiring.package=org.jboss.logging)(version>=3.1.0)(!(version>=4.0.0)))
     |
    export: osgi.wiring.package=org.jboss.logging
  org.ops4j.pax.logging.pax-logging-api [7.0]

Chain 2:
  org.jboss.integration.fuse.switchyard-component-common-knowledge [420.0]
    import: (&(osgi.wiring.package=org.switchyard.config.model.composite.v1)(version>=2.0.0)(!(version>=3.0.0)))
     |
    export: osgi.wiring.package=org.switchyard.config.model.composite.v1; uses:=org.jboss.logging
  org.switchyard.switchyard-config [353.0]
    import: (&(osgi.wiring.package=org.jboss.logging)(version>=3.1.0)(!(version>=4.0.0)))
     |
    export: osgi.wiring.package=org.jboss.logging
  org.jboss.logging.jboss-logging [326.0]

      Tested with builds 249, 251 and 253 with the same result. Note that all my steps work fine with the build 224 which was release as 6.3.0.R1.

              ggrzybek Grzegorz Grzybek
              apodhrad@redhat.com Andrej Podhradsky
              Stefan Veres Stefan Veres (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: