[jira] [Commented] (MNG-6080) New scope for non-functional dependencies

["Michael Osipov (JIRA)" <ji...@apache.org>]

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

Michael Osipov commented on MNG-6080:
-------------------------------------

It should also be mentioned that ZIP files are treated as first-class citizens by {{java(1)}}. In your case, any decent web framework offers to serve static files from classpath (Spring does) or the Servlet 3.0 spec provides auto-deployment of static files from {{/META-INF/resources}} in a JAR file, removing the need to unpack them to the WAR file at all.

Can you elaborate on the difference between both proposed scopes? What impact would they have actually in the reactor, dependency consumption and (test) classpath composition?

> New scope for non-functional dependencies
> -----------------------------------------
>
>                 Key: MNG-6080
>                 URL: https://issues.apache.org/jira/browse/MNG-6080
>             Project: Maven
>          Issue Type: New Feature
>          Components: Dependencies
>    Affects Versions: 3.3.9
>            Reporter: Paul Benedict
>            Assignee: Paul Benedict
>            Priority: Critical
>
> Maven currently lacks a scope for artifacts that should not be part of the classpath. The classpath is the path that the Java Runtime Environment (JRE) searches for classes and other resource files. Given that the classpath is Java specific, this feature request can be generalized to accommodate artifacts that are not code related (directly or indirectly). It is neither code that executes (like a .class file = "directly") nor a resource file intimately linked to executable code (like a .properties file = "indirectly").
> For example, an organization may with to establish a Maven project that contains common look-and-feel elements to brand all their web applications. This project could be a ZIP archive to be included in downstream projects, in which each build explodes the archive into their respective web application context roots.
> Two names in the running for the new scope are {{"asset"}} and {{"reactor"}}. They are nearly equal but have a different slight emphasis. The {{"asset"}} name emphasizes purpose of artifact. The {{"reactor"}} name emphasizes purpose within the build. The Maven Team should decide among these two or propose a third. 
> Thread where discussion originated:
> http://mail-archives.apache.org/mod_mbox/maven-dev/201608.mbox/%3CCABLGb9x5e3fE25Qj9DwvCsCSa1Dwe_e6%2BOmWjL0ZbQ07HLEm8g%40mail.gmail.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)