A. J. David Bosschaert created SLING-9180:
---------------------------------------------
Summary: Wrong regions reported when API Regions removes a
candidate
Key: SLING-9180
URL: https://issues.apache.org/jira/browse/SLING-9180
Project: Sling
Issue Type: Bug
Components: Feature Model
Affects Versions: Feature Model API Regions Runtime Fragment 1.0.8
Reporter: A. J. David Bosschaert
Assignee: A. J. David Bosschaert
Fix For: Feature Model API Regions Runtime Fragment 1.0.10
The API Regions runtime fragment reports a warning when a candidate is removed
from the resolution set.
This reporting incorrectly contains too many region names. Instead of just the
region where the package is exported in, it could also be reporting other
regions that the exporting feature is exporting into.
It could be reporting something like this:
{code:java}
WARNING: API-Regions removed candidates some.bundle [Regions: [org.foo.bar,
global], Feature: f2] for requirement some.other.bundle package org.sling.mypkg
as the requirement is in the following regions: [org.foo.blah, global] and in
feature: [f1]
{code}
When the exported package {{org.sling.mypkg}} is actually _only_ in the
_org.foo.bar_ region, and not in the global region.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
