You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Christian Schulte (JIRA)" <ji...@apache.org> on 2016/02/15 14:24:18 UTC
[jira] [Closed] (MNG-5978) test libraries should declare expected
scope in their pom
[ https://issues.apache.org/jira/browse/MNG-5978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Schulte closed MNG-5978.
----------------------------------
Resolution: Not A Problem
That's what you use dependency management for. Just put {{<scope>test</scope>}} into {{<dependencyManagement>}} and Maven will use that scope everywhere no scope has been declared explicitly.
> test libraries should declare expected scope in their pom
> ---------------------------------------------------------
>
> Key: MNG-5978
> URL: https://issues.apache.org/jira/browse/MNG-5978
> Project: Maven
> Issue Type: Wish
> Components: Dependencies
> Reporter: Nadav Wexler
>
> when using test libraries and forgetting to include the expected <scope>test</scope> this could have your jars and wars inflated and could also create some problems in your environment.
> I suggest to include the expected scope in your pom, and then when depending on that library, checking against the actual pom.
> if those do not match then a warning should be triggered.
> also this should be recursive - the check should not emit a warning if the using library is also a test library.
> I'd love to hear your comments on this Wish!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)