maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <>
Subject [jira] [Commented] (MNG-6080) New scope for non-functional dependencies
Date Tue, 16 Aug 2016 06:39:21 GMT


Michael Osipov commented on MNG-6080:

{{compile}}? You probably mean {{provided}}. This won't end up in the output.

> New scope for non-functional dependencies
> -----------------------------------------
>                 Key: MNG-6080
>                 URL:
>             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:

This message was sent by Atlassian JIRA

View raw message