You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/10/02 10:26:00 UTC

[jira] [Commented] (MNG-7547) Simplify G level metadata handling

    [ https://issues.apache.org/jira/browse/MNG-7547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17612065#comment-17612065 ] 

ASF GitHub Bot commented on MNG-7547:
-------------------------------------

gnodet commented on PR #806:
URL: https://github.com/apache/maven/pull/806#issuecomment-1264606254

   The branch http://github.com/gnodet/maven/tree/plugin-metadata fixes the conflict and also remove the metadata from the v4 api.




> Simplify G level metadata handling
> ----------------------------------
>
>                 Key: MNG-7547
>                 URL: https://issues.apache.org/jira/browse/MNG-7547
>             Project: Maven
>          Issue Type: Improvement
>          Components: Artifacts and Repositories, Plugins and Lifecycle
>            Reporter: Tamás Cservenák
>            Assignee: Tamás Cservenák
>            Priority: Major
>             Fix For: 3.9.0, 4.0.0-alpha-1, 4.0.0
>
>
> The original fix from MNG-7055 can be tremendously simplified: the plugins about to be deployed are JARs with embedded plugin descriptor, that contains all the required information (GA, prefix, name) to make G level metadata generator does everything on it's own, no need for hoops and loops at all. Actually, with this, all 3 generators becomes self-sufficient, and no need for caller to even fiddle with deploying metadata (as it happens automatically, courtesy of resolver and resolver-provider in maven).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)