You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Tamas Cservenak (Jira)" <ji...@apache.org> on 2024/05/07 13:39:00 UTC

[jira] [Updated] (MNG-8117) Improve prerequisite evaluation and plugin version selection logging

     [ https://issues.apache.org/jira/browse/MNG-8117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tamas Cservenak updated MNG-8117:
---------------------------------
    Description: 
Currently, when user uses {{G:A}} the plugin tried is {{G:A:LATEST}} and is checked for "compatibility" (Maven prerequisite in Maven3 and Maven4, plus for Java prerequisite in Maven4 only). This may lead that "latest" (by Maven Metadata) version is not compatible, and Maven will cycle toward older versions. But the console output is a mess.

Current output can be seen in this gist: [https://gist.github.com/cstamas/e44a2e51f5ec9f2e803dfb1d487d2fd5]

PR creates output like this: https://gist.github.com/cstamas/3ca4bc6cea5f701054061871b5db3f35

  was:Currently, when user uses {{G:A}} the plugin tried is {{G:A:LATEST}} and is checked for "compatibility" (Maven prerequisite in Maven3 and Maven4, plus for Java prerequisite in Maven4 only). This may lead that "latest" (by Maven Metadata) version is not compatible, and Maven will cycle toward older versions. But the console output is a mess.


> Improve prerequisite evaluation and plugin version selection logging
> --------------------------------------------------------------------
>
>                 Key: MNG-8117
>                 URL: https://issues.apache.org/jira/browse/MNG-8117
>             Project: Maven
>          Issue Type: Improvement
>          Components: Plugins and Lifecycle
>            Reporter: Tamas Cservenak
>            Priority: Major
>             Fix For: 4.0.0, 4.0.0-beta-1
>
>
> Currently, when user uses {{G:A}} the plugin tried is {{G:A:LATEST}} and is checked for "compatibility" (Maven prerequisite in Maven3 and Maven4, plus for Java prerequisite in Maven4 only). This may lead that "latest" (by Maven Metadata) version is not compatible, and Maven will cycle toward older versions. But the console output is a mess.
> Current output can be seen in this gist: [https://gist.github.com/cstamas/e44a2e51f5ec9f2e803dfb1d487d2fd5]
> PR creates output like this: https://gist.github.com/cstamas/3ca4bc6cea5f701054061871b5db3f35



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