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

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

rmannibucau commented on PR #995:
URL: https://github.com/apache/maven/pull/995#issuecomment-1424752367

   > 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.
   
   
   Point is none can be hardcoded, cause we dont know companies mirrors.
   This is why it fits a plugin better IMO (wouldnt be great to have that in 
maven imo).
   
   If you dont like the plugin, what about doing a `mvn-install-checker` 
project or extension which can grow and be downloaded at need.
   Thing is this code requires config and ultimately shouldnt be a command but 
more explicit error messages when it fails IMHO.
   Current flavor looks like not scaling well in time/hard to maintain in a 
relevant manner and is already biased due to profiles so a checker or plugin 
looks iso without the pitfall to impact core directly when you ll need to check 
proxy certs, proxy protocol, proxy passwords, sftp cert for deployment, 
properties typos in settings etc....(this is where this command/plugin/helper 
will lead if adopted).




> 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)

Reply via email to