[MNG-6080] New scope for non-functional dependencies

**[Paul Benedict](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=paul4christ79)** opened **[MNG-6080](https://issues.apache.org/jira/browse/MNG-6080?redirect=false)** and commented

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

---

**Affects:** 3.3.9

**Issue Links:**
- [MNG-5567](https://issues.apache.org/jira/browse/MNG-5567) Zip files are not included in classpaths at all

0 votes, 6 watchers

Start by reading MNG-6080, its linked MNG-5567 issue, and the referenced Maven-dev discussion. The issue does not name implementation files or tests; first clarify the intended scope name and expected handling of non-code artifacts, then identify the affected Maven build and classpath behavior. Done means the team has agreed on the scope semantics and the resulting behavior is covered.

Written by the indexing model from the issue text.