aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom De Wolf (JIRA)" <>
Subject [jira] [Commented] (ARIES-1588) Installation of subsystems fails due to uses constraint violation after exposing feature capabilities.
Date Tue, 14 Mar 2017 13:25:41 GMT


Tom De Wolf commented on ARIES-1588:

[~tjwatson] [] using pull request
I kept the fix for ARIES-1442 and even fixed the case for the FragmentHost capability which
a subsystem should also not impersonate. Additionally, at installation time it should not
expose the capabilities of its contituents because it will conflict with the LocalRepository
in which the resolver then also finds a resource capable of doing the same resulting in these
resolve chain conflicts. 

Can someone have a look at the pull request? thx

Then we can release 2.1.0 and get all the work being done out there.

> Installation of subsystems fails due to uses constraint violation after exposing feature
> ------------------------------------------------------------------------------------------------------
>                 Key: ARIES-1588
>                 URL:
>             Project: Aries
>          Issue Type: Bug
>          Components: Subsystem
>    Affects Versions: subsystem-2.1.0
>            Reporter: Wouter Bancken
>             Fix For: subsystem-2.1.0
>         Attachments: pax-web-jetty-bundle-4.2.5.jar
> h4. Setup
> Two feature subsystems
> 1. Feature subsystem with fragment-hosts and fragments
> 2. Feature subsystem with other bundles
> Installation of the second subsystem fails
> h4. Issue
> Installation of the second subsystem fails with the message 
> {quote}
> gogo: SubsystemException: org.osgi.service.resolver.ResolutionException: Uses constraint
violation. Unable to resolve resource org.ops4j.pax.web.pax-web-jetty-bundle [124.0] because
it exports package 'org.apache.xbean.finder.archive' and is also exposed to it from resource
org.apache.xbean.finder [98.0] via the following dependency chain:
> org.ops4j.pax.web.pax-web-jetty-bundle [124.0]
> import: (osgi.wiring.package=org.apache.xbean.finder)
> export: osgi.wiring.package: org.apache.xbean.finder; uses:=org.apache.xbean.finder.archive
> export: osgi.wiring.package=org.apache.xbean.finder.archive
> org.apache.xbean.finder [98.0]
> {quote}
> Before failing a lot of similar messages are logged with the message "DEBUG: Candidate
permutation failed due to a conflict between an export and import; will try another if possible."
> This is especially weird since pax-web-jetty-bundle does not expose the org.apache.xbean.finder.archive
package (see attached Jar). Both pax-web-jetty-bundle and org.apache.xbean.finder are only
present in the first subsystem.
> In our setup pax-web-jetty-bundle is a fragment-host for a fragment which is in the same
(first) subsystem. Similar DEBUG statements are printed for other fragment-hosts in the first
> The issue occurs since commit 4c0437de06f34321909a6132a7f2be163b2f6d5 (ARIES-1443). In
earlier versions, we had no issues for these subsystems. 

This message was sent by Atlassian JIRA

View raw message