Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Unresolved constraint in bundle org.opennms.features.vaadin-node-maps

Description

ERROR: Bundle org.opennms.features.vaadin-node-maps [80] Error starting mvn:org.opennms.features/vaadin-node-maps/1.13.0-SNAPSHOT (org.osgi.framework.BundleException: Unresolved constraint in bundle org.opennms.features.vaadin-node-maps [80]: Unable to resolve 80.0: missing requirement [80.0] osgi.wiring.package; (&(osgi.wiring.package=org.apache.commons.io)(version>=1.4.0)(!(version>=2.0.0))))
org.osgi.framework.BundleException: Unresolved constraint in bundle org.opennms.features.vaadin-node-maps [80]: Unable to resolve 80.0: missing requirement [80.0] osgi.wiring.package; (&(osgi.wiring.package=org.apache.commons.io)(version>=1.4.0)(!(version>=2.0.0)))
at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:3826)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1868)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1191)
at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:295)
at java.lang.Thread.run(Thread.java:679)

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Seth Leger November 22, 2013 at 3:40 PM

This was caused by an incorrect system bundle export in Karaf. commons-io exposes their API with 2 separate version numbers and we needed to differentiate between the two versions in our system bundle exports in container/karaf/src/main/filtered-resources/etc/custom.properties. Marking as fixed.

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

PagerDuty

Created October 7, 2013 at 6:16 PM
Updated January 21, 2015 at 7:52 PM
Resolved November 22, 2013 at 3:40 PM

Flag notifications