[jira] [Resolved] (SLING-9738) Allow to mark api deprecated as part of the api region

["Carsten Ziegeler (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-9738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-9738.
-------------------------------------
    Resolution: Fixed

Implemented in https://github.com/apache/sling-org-apache-sling-feature-extension-apiregions/commit/4bf6acbba8c4759406242b75c28940b5ad985731

added new unit tests

documented in https://github.com/apache/sling-org-apache-sling-feature-extension-apiregions/blob/master/docs/api-regions.md

> Allow to mark api deprecated as part of the api region
> ------------------------------------------------------
>
>                 Key: SLING-9738
>                 URL: https://issues.apache.org/jira/browse/SLING-9738
>             Project: Sling
>          Issue Type: New Feature
>          Components: Feature Model
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>            Priority: Major
>             Fix For: Feature Model API Regions Extension 1.1.8
>
>
> With the API regions we have a mechanism to create different groups of api like for example an internal and a public/global api.
> There are use cases where you want to deprecate public api, but - for it's not possible to mark that api as deprecated in the source. The deprecation is only for the project using/providing those regions.
> For such cases, it makes sense to add deprecation information to the api region of the feature model - which then can be used by additional tooling - or at runtime etc.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)