You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2022/06/24 12:16:00 UTC

[jira] [Commented] (SLING-11411) Remove scope from dependency management

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

Konrad Windszus commented on SLING-11411:
-----------------------------------------

This is an example output from https://github.com/apache/sling-org-apache-sling-api/pull/44:

 !Screenshot 2022-06-24 at 14.11.25.png! 

> Remove scope from dependency management
> ---------------------------------------
>
>                 Key: SLING-11411
>                 URL: https://issues.apache.org/jira/browse/SLING-11411
>             Project: Sling
>          Issue Type: Improvement
>          Components: General
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>            Priority: Major
>             Fix For: Parent 49, Bundle Parent 49
>
>         Attachments: Screenshot 2022-06-24 at 14.11.25.png
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Managing the scope in the depMgmt is an [anti-pattern|https://stackoverflow.com/a/20750041], as it makes it very hard to override the scope. Therefore all scopes should be removed from the dependency management in the parent poms and at the same time it should be enforced that the scope is always explicitly set locally with an enforcer rule (SLING-11410)



--
This message was sent by Atlassian Jira
(v8.20.7#820007)