You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (Jira)" <ji...@apache.org> on 2026/02/14 13:48:00 UTC
[jira] [Resolved] (SLING-13114) Check for deprecated API does not consider other bundles exporting the API
[ https://issues.apache.org/jira/browse/SLING-13114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved SLING-13114.
--------------------------------------
Resolution: Fixed
Rewrote the handling of these packages in case of multiple bundles providing it. If a different feature than the feature deprecating the API provides a matching packages, this is considered now ok and not flagged
> Check for deprecated API does not consider other bundles exporting the API
> --------------------------------------------------------------------------
>
> Key: SLING-13114
> URL: https://issues.apache.org/jira/browse/SLING-13114
> Project: Sling
> Issue Type: Bug
> Components: Feature Model
> Affects Versions: Feature Model API Regions Extension 2.1.0
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Priority: Major
> Fix For: Feature Model API Regions Extension 2.1.2
>
>
> If a package is deprecated in one feature model but another feature model provides the same package via a different bundle, either in the same version or another version - this is currently not considered - and always the usage of the deprecated API is reported.
> There are two cases:
> - another feature provides the API in a different (newer) version - in this case the using bundle is usually not even wired to the deprecated API.
> - another feature provides the API in the same version - while the using bundle could be wired to the one where the package is deprecated, it is still ok (no warning/error) as the other feature provides an undeprecated version of the API.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)