[
https://issues.apache.org/jira/browse/MNG-7869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761813#comment-17761813
]
Tamas Cservenak edited comment on MNG-7869 at 9/4/23 12:37 PM:
---------------------------------------------------------------
Hashes does not need to be calculated every time, only when executing -v (as it
is completely different exec branch, and unlike -V it exits).
Also, our users almost always provide mvn -v output, while this plugin would
need an extra rountrip (and internet access, and whatever, something not always
available ie. in confined/air gapped environment)....
But yes, plugin could do it too.
was (Author: cstamas):
Hashes does not need to be calculated every time, only when executing -v (as it
is completely different exec branch, and unlike -V it exists).
Also, our users almost always provide mvn -v output, while this plugin would
need an extra rountrip (and internet access, and whatever, something not always
available ie. in confined/air gapped environment)....
But yes, plugin could do it too.
> Improve mvn -v output
> ---------------------
>
> Key: MNG-7869
> URL: https://issues.apache.org/jira/browse/MNG-7869
> Project: Maven
> Issue Type: Task
> Reporter: Tamas Cservenak
> Priority: Major
>
> This is really just a dream or wish: would be good if mvn -v (output we
> usually ask from users) would show us more than today, to be able to detect
> like "tampering with resolver" (or replacing it), possible core extensions,
> etc...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
