[
https://issues.apache.org/jira/browse/MNG-7924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17784421#comment-17784421
]
ASF GitHub Bot commented on MNG-7924:
-------------------------------------
cstamas commented on PR #1299:
URL: https://github.com/apache/maven/pull/1299#issuecomment-1803725216
Just a thought experiment (that takari somewhat tried to deliver): Look at
the `takari-maven-component` packaging. It's goal is: producing jar artifact
meant to be used within Maven.
This is so expressive... what are you building? "maven-component"s or "jar
with sisu index to be used in Maven".
Basically, we could distinguish even "jar with sisu index", and if user
depends on that, it could (by some plugin, surefire extension example) trigger
Sisu container creation that uses INDEX to pick up components from classpath,
and so on and so on... These little information crumbs can serve the purpose to
make things even more smarter (without being "smart smart", but simply to
behave according things our user describes to us).
Also, they express intent very very clearly.
> Better control over and better integration with Resolver
> --------------------------------------------------------
>
> Key: MNG-7924
> URL: https://issues.apache.org/jira/browse/MNG-7924
> Project: Maven
> Issue Type: Task
> Components: Artifacts and Repositories
> Reporter: Tamas Cservenak
> Priority: Major
> Fix For: 4.0.0-alpha-9
>
>
> Integrate better and obtain better control over Resolver. These changes did
> stem from "[JPMS module
> experiment|https://cwiki.apache.org/confluence/display/MAVEN/Experiment+-+Explicit+JPMS+support]";
> and are considered improvement but *does not implement any functionality*
> related to JPMS module support.
> Changes:
> * Maven4 should stop "disconnected coexistence" of two type systems
> (ArtifactHandlers and Resolver ArtifactTypeRegistry), it should unify them.
> * Maven4 Core should provide generic and extensible means to introduce new
> artifact types (fully in extension, and extension should get extended data
> via "roundtrip" in core/resolver)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
