[
https://issues.apache.org/jira/browse/MNG-7869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761798#comment-17761798
]
Tamas Cservenak commented on MNG-7869:
--------------------------------------
Example (imagined) output with 2nd method:
{noformat}
$ mvn -v
Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
Maven home: /home/cstamas/.sdkman/candidates/maven/current
(dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9) <- some plaf independent hash of
all things under maven.home
Java version: 17.0.8.1, vendor: Eclipse Adoptium, runtime:
/home/cstamas/.sdkman/candidates/java/17.0.8.1-tem
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "6.4.13-200.fc38.x86_64", arch: "amd64", family:
"unix"
$
{noformat}
> 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)
