[
https://issues.apache.org/jira/browse/MNG-6869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17686729#comment-17686729
]
ASF GitHub Bot commented on MNG-6869:
-------------------------------------
mthmulders commented on PR #995:
URL: https://github.com/apache/maven/pull/995#issuecomment-1424703182
> Isnt it something a plugin would be a better location?
The current approach does not need any additional download. I think that's a
good thing, as we can now use it to also point the user at issues in their
configuration that would prevent artifact resolution. If we moved this to a
plugin, we'd need artifact resolution to actually work...
> Can need some basic downloads but would enable to do more checks on the
project, better configure the dummy artifact - 3.8.6 or maven cant be hardcoded
in case of central "mirroring", it can be forbidden intentionally.
I'm open to suggestions for another publicly available artifact. But in
order to "prove" that artifact resolution works, we need something that is
publicly available - I think something that at the very least is hosted by
Central, and maybe by mirrors.
> It would also enable to maje checks grow, in particular with coming
multilocal repo feature for ex.
More thorough checks could reside in a plugin, but as pointed out before, we
can't rely on resolution to work until we've checked that it works. So agreed,
additional checks could live in a plugin, but I'm convinced that we'll need a
few basic checks (among them artifact resolution and local repository setup) to
live in Core.
> 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)
