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:15:00 UTC

[jira] [Commented] (SLING-11410) Maven enforcer rule which checks that all dependencies have an explicit scope set

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

Konrad Windszus commented on SLING-11410:
-----------------------------------------

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! 

> Maven enforcer rule which checks that all dependencies have an explicit scope set
> ---------------------------------------------------------------------------------
>
>                 Key: SLING-11410
>                 URL: https://issues.apache.org/jira/browse/SLING-11410
>             Project: Sling
>          Issue Type: New Feature
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>            Priority: Major
>             Fix For: Maven Enforcer Rules 1.1.0
>
>         Attachments: Screenshot 2022-06-24 at 14.11.25.png
>
>
> Useful in case when the scope is no longer part of the dependencyManagement or in general to force making developers a distinct decision (prevents the default scope compile from being used for test dependencies).
> For some background read https://lists.apache.org/thread/srm5cbfjn1004ql4c5k6mgbp1t684zc0



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