[
https://issues.apache.org/jira/browse/MNG-6080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15421659#comment-15421659
]
Paul Benedict commented on MNG-6080:
------------------------------------
Michael, you are right that ZIP files are treated as first-class citizens on
the classpath. Just for the sake of quoting something official to backup your
point, here's a good line from Java documentation: ["Class path entries that
are neither directories nor archives (.zip or JAR files) nor the asterisk (*)
wildcard character are
ignored."|https://docs.oracle.com/javase/8/docs/technotes/tools/windows/classpath.html]
Regarding your first question, I am only proposing one scope. The two names are
just potential choices ... with some philosophical waxing by me on the
meanings/suggestions/implications behind the words. I hope that whatever name
is chosen, it best captures the purpose of the scope.
Regarding your second question, the new scope should act like "compile" except
it has no classpath entry. Plugins should not attempt to add it to any language
execution environment.
> 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)
