[
https://issues.apache.org/jira/browse/MNG-7620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644264#comment-17644264
]
Romain Manni-Bucau commented on MNG-7620:
-----------------------------------------
Guess with the new v4 api it will mainly be a matter of taking what is exported
from maven-core (v4 api impl) + optionally added by extensions and be it.
Side note: for v3 plugin we must keep the legacy behavior of exporting or not
based on a predefined list (+ext).
> Rework how "exportedArtifacts" works
> ------------------------------------
>
> Key: MNG-7620
> URL: https://issues.apache.org/jira/browse/MNG-7620
> Project: Maven
> Issue Type: Improvement
> Reporter: Christoph Läubrich
> Priority: Major
>
> Recently there was a discussion about "exportedArtifacts" and how the work
> here are the relevant code path:
> https://github.com/apache/maven/blob/master/maven-core/src/main/java/org/apache/maven/classrealm/DefaultClassRealmManager.java#L302-L328
> https://github.com/apache/maven/blob/master/maven-core/src/main/java/org/apache/maven/classrealm/DefaultClassRealmManager.java#L83-L87
> First the documentation is a bit misleading, as it says
> {code:java}
> Patterns of artifacts provided by maven core and exported via maven api realm
> {code}
> from some experiments, it seems that any core or project extension can also
> define "exported" artifacts.
> Second is, that this simply adds the URL of an exported artifact and thus
> always the same *jar* is used to load the class, but still different
> classrealms can load the class.
> What came into my mind is that it actually should have an own realm where
> such exported artifacts are loaded and this realm is then imported instead of
> the URL.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
