You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Elliotte Rusty Harold (Jira)" <ji...@apache.org> on 2019/12/16 12:07:00 UTC

[jira] [Commented] (MNG-6120) Allow changing of default scope and change the default scope

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

Elliotte Rusty Harold commented on MNG-6120:
--------------------------------------------

I think setting the default to runtime would be a non starter for most projects. 

> Allow changing of default scope and change the default scope
> ------------------------------------------------------------
>
>                 Key: MNG-6120
>                 URL: https://issues.apache.org/jira/browse/MNG-6120
>             Project: Maven
>          Issue Type: Wish
>            Reporter: Caleb Cushing
>            Priority: Major
>
> Recently I've realized that a lot of what jigsaw will provide regarding transient dependencies can be resolved in maven if you use <dependencyManagement> and set the default scope for each dep to runtime, and then override that where you actually want compile time dependencies. I think it would be nice if you could easily set the default scope for all modules (meaning those that don't specify scope) to runtime (or compile, or whatever), and then set the default to runtime in the next major maven version (4?).
> Even if I only got the ability to set that default scope that'd be great.



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