Bug 1136104

Summary: ModeShape JCR invalid OSGi meta-data
Product: [JBoss] JBoss Data Virtualization 6 Reporter: Julian Coleman <jcoleman>
Component: ModeShapeAssignee: Horia Chiorean <hchiorea>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: dlesage, fnguyen, vhalbert
Target Milestone: ER4Keywords: QA-Closed
Target Release: 6.1.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
The ModeShape JCR jar (version 3.8.1) contained invalid OSGi meta-data. This lead to errors when it was loaded in an OSGi container. TGo fix this problem the org.modeshape.common.util has been changed so that it does not depend on dependencies in modeshape-jcr*jar anymore. As a result, these errors no longer arise.
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-10 08:52:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Description Flags
OSGi bundle workaround none

Description Julian Coleman 2014-09-01 19:37:06 UTC
The ModeShape JCR jar (version 3.8.1) contains invalid OSGi meta-data.  This leads to errors with loading it in an OSGi container:

> Error executing command: Could not start bundle mvn:org.modeshape/modeshape-jcr/3.8.1.GA-redhat-1 in feature(s) s-ramp-dependencies-0.5.0.Beta3-redhat-1: Uses constraint violation. Unable to resolve bundle revision org.modeshape.jcr [551.0] because it exports package 'org.modeshape.common.util' and is also exposed to it from bundle revision org.modeshape.common [550.0] via the following dependency chain:
>   org.modeshape.jcr [551.0]
>     import: (&(osgi.wiring.package=org.modeshape.common)(version>=3.8.0)(!(version>=4.0.0)))
>      |
>     export: osgi.wiring.package=org.modeshape.common; uses:=org.modeshape.common.util
>     export: osgi.wiring.package=org.modeshape.common.util
>   org.modeshape.common [550.0]

It looks like this is because the source contains a class under org.modeshape.common.util, and there are also classes under org.modeshape.common.util in the modeshape-common module.  This causes the OSGi export entry in MANIFEST.MF:


which clashes with the (different) org.modeshape.common.util entry in the modeshape-common jar:


There are other classes not under org.modeshape.jcr, for example:


but these don't appear to clash with other jars currently.

Comment 2 Julian Coleman 2014-09-01 19:42:06 UTC
Created attachment 933517 [details]
OSGi bundle workaround

Workaround patch overriding the parent bundle configuration.

Comment 5 Horia Chiorean 2014-09-04 05:09:24 UTC
Fixed and merged into the product branch for DV 6.1: https://github.com/jboss-integration/modeshape/commit/807e12e1411a12c3e376c0b522062779620fd6d4

Comment 6 Filip Nguyen 2015-02-03 11:15:52 UTC
Verified. The org.modeshape.common.util doesn't define dependencies in modeshape-jcr*jar anymore.