[
https://issues.apache.org/jira/browse/MNG-8026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17810837#comment-17810837
]
ASF GitHub Bot commented on MNG-8026:
-------------------------------------
rmannibucau commented on code in PR #1391:
URL: https://github.com/apache/maven/pull/1391#discussion_r1466206736
##########
api/maven-api-core/src/main/java/org/apache/maven/api/Artifact.java:
##########
@@ -105,6 +105,14 @@ default String key() {
*/
boolean isSnapshot();
+ /**
+ * The artifact properties.
+ *
+ * @return the artifact properties, never {@code null}
+ */
+ @Nonnull
+ ArtifactProperties getArtifactProperties();
Review Comment:
We need open properties (my 2cts would be it is `Map<String, Object>`, no
need to type it stronger) to enable a (custom) type - I include the
"module-jar" kind of types, ie all but extensions types - to complete the meta
of a dependency - the old artifact handler somehow which is propagated to
properties.
Having or not a wrapper is a style choice but we already have some
properties (is added to classpath etc) no?
> Maven should define from ground up scopes used with Resolver
> ------------------------------------------------------------
>
> Key: MNG-8026
> URL: https://issues.apache.org/jira/browse/MNG-8026
> Project: Maven
> Issue Type: Task
> Reporter: Tamas Cservenak
> Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-13
>
>
> See MRESOLVER-471, it is actually role of Maven (as a resolver consumer
> project) to define all these things:
> * supported scopes
> * transformations of scopes to build path scopes
> * fine tune conflict resolution and related things (in session)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
