You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@apache.org> on 2018/12/29 11:03:00 UTC

[jira] [Commented] (MNG-6545) Scope runtime test

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

Robert Scholte commented on MNG-6545:
-------------------------------------

This will probably depend on the build/consumer-pom. This will ensure that only known scopes end up in the poms in Maven Central and other remote repositories.

> Scope runtime test
> ------------------
>
>                 Key: MNG-6545
>                 URL: https://issues.apache.org/jira/browse/MNG-6545
>             Project: Maven
>          Issue Type: Improvement
>          Components: Dependencies
>            Reporter: Olivier Cailloux
>            Priority: Minor
>
> Maven should permit to include a dependency with scope restricted to test and runtime. Currently we have to choose between test and runtime, having both would be better.
> It would permit Maven to check that the test code does not depend (for compilation) on those libraries. And you wouldn’t get annoyed by completion proposals in your IDE coming from those runtime libraries.
> It is also conceptually more elegant and would make the intent clear to other contributers (“make sure your test code does not depend on this library”).
> Also discussed [here|https://mail-archives.apache.org/mod_mbox/maven-users/200811.mbox/%3c17608340.3674701226307519843.JavaMail.adm-moff@moffice8.nsc.no%3e] and [here|https://stackoverflow.com/a/27729783].



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)