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 2023/05/10 08:41:00 UTC

[jira] [Commented] (MNG-6934) Suggest plugin upgrade in case of failure

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

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

Giovds commented on PR #1087:
URL: https://github.com/apache/maven/pull/1087#issuecomment-1541587954

   I don't think there are unnecessary connections as they are required to check if the plugin is using the latest version _if the Jira ticket is still something Maven wants to provide_. I don't think you can resolve this issue within Maven without outbound connections?
   
   An alternative could be to check only the local repository, but I don't think this is a good idea as the user may or may not have higher versions of the plugin installed.
   
   Or it could just log a suggestion like: "Please consider checking you are using the latest version of the 'xxx' plugin", however that kind of defeats the purpose of automatically checking for newer version.




> Suggest plugin upgrade in case of failure
> -----------------------------------------
>
>                 Key: MNG-6934
>                 URL: https://issues.apache.org/jira/browse/MNG-6934
>             Project: Maven
>          Issue Type: Improvement
>            Reporter: Robert Scholte
>            Priority: Major
>
> In case a plugin fails, Maven should look if there is a more recent version.
> It is considered the best practice to verify the most recent version first before issueing a but, as it might already be solved.
> The be clear: if the most recent plugin is used, this message should not be shown.
> Make use of the metadata to get the most recent version.



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