[
https://issues.apache.org/jira/browse/MNG-6869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17692686#comment-17692686
]
ASF GitHub Bot commented on MNG-6869:
-------------------------------------
mthmulders commented on PR #995:
URL: https://github.com/apache/maven/pull/995#issuecomment-1441813122
Personally, I don't see much value in moving the code to a new module. If I
understand correctly, we'd be moving this code to a different module inside the
same Git repository, only to introduce some complexity in maven-embedder to
load that exact same code. Also, this PR doesn't pull in new dependencies to
maven-embedder, which we could have avoided by moving the code elsewhere, so I
really fail to see the benefits of such a refactoring.
> New flag to verify the status
> -----------------------------
>
> Key: MNG-6869
> URL: https://issues.apache.org/jira/browse/MNG-6869
> Project: Maven
> Issue Type: New Feature
> Reporter: Robert Scholte
> Assignee: Maarten Mulders
> Priority: Major
>
> While working on INFRA-19861 we had issues with invalid changes in the
> settings.xml.
> This was detected too late. After installation {{mvn --version}} is called,
> but it will only show the version of Maven.
> It would be better to have a flag that verifies it a bit more:
> - can Maven read/write to the local repository
> - can Maven access all predefined repositories? (does the proxy work?)
> This gives a much better feedback if Maven can do its job.
> Current workaround: call something like {{mvn help:evaluate
> -Dexpression=settings.localRepository -q -DforceStdout}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
