Unable to resolve external dependency when using --lib option.

Solution Verified - Updated -

Issue

  • We have a Camel application that has an external dependency. We deploy the application to a Fabric using a profile where we define a bundle as a reference to the jar in the local maven repo.We install the application bundle and the dependency in the local maven repo. Then we use the following commands in the Fuse console:
fabric:profile-create --parent feature-camel logger-profile
fabric:profile-edit --feature camel-amq --bundle mvn:org.jboss.quickstarts.fuse/beginner-camel-log/6.2.0.redhat-133 --lib mvn:com.test.xxx/yyy/2.2.6 logger-profile
fabric:container-create-child --profile logger-profile root logger
  • The container then fails to start with the following error:
org.osgi.service.resolver.ResolutionException: Unable to resolve root: missing requirement [root] osgi.identity; osgi.identity=org.jboss.quickstarts.fuse.beginner-camel-log; type=osgi.bundle; version="[6.2.0.redhat-133,6.2.0.redhat-133]"; resolution:=mandatory [caused by: Unable to resolve org.jboss.quickstarts.fuse.beginner-camel-log/6.2.0.redhat-133: missing requirement [org.jboss.quickstarts.fuse.beginner-camel-log/6.2.0.redhat-133] osgi.wiring.package; filter:="(osgi.wiring.package=com.test.xxx)"]

Environment

  • Red Hat JBoss Fuse
    • 6.2.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.