Installation of subsystems fails due to uses constraint violation after exposing feature capabilities.

Setup

Two feature subsystems
1. Feature subsystem with fragment-hosts and fragments
2. Feature subsystem with other bundles
Installation of the second subsystem fails

Issue

Installation of the second subsystem fails with the message

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]

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 subsystem.

The issue occurs since commit 4c0437de06f34321909a6132a7f2be163b2f6d5 (ARIES-1443). In earlier versions, we had no issues for these subsystems.