You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Roy Teeuwen (Jira)" <ji...@apache.org> on 2022/01/17 20:32:00 UTC

[jira] [Commented] (SLING-11068) Split up api regions exportsimports analyser task

    [ https://issues.apache.org/jira/browse/SLING-11068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477398#comment-17477398 ] 

Roy Teeuwen commented on SLING-11068:
-------------------------------------

Created PR: https://github.com/apache/sling-org-apache-sling-feature-extension-apiregions/pull/17

> Split up api regions exportsimports analyser task
> -------------------------------------------------
>
>                 Key: SLING-11068
>                 URL: https://issues.apache.org/jira/browse/SLING-11068
>             Project: Sling
>          Issue Type: Improvement
>          Components: Feature Model Analyser
>            Reporter: Roy Teeuwen
>            Priority: Major
>
> Currently the api region exportsimports analyser task does two things, namely check if any packages has any unversioned exports / imports and if the regions can import specific packages. These are two separate tasks that could be split up so that you can more easily ignore one of both. One of the examples where you would want to ignore this is when the import package contains unversioned ranges in a third party bundle, which is not easily fixable



--
This message was sent by Atlassian Jira
(v8.20.1#820001)