[
https://issues.apache.org/jira/browse/MNG-6869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17721357#comment-17721357
]
ASF GitHub Bot commented on MNG-6869:
-------------------------------------
mthmulders commented on code in PR #995:
URL: https://github.com/apache/maven/pull/995#discussion_r1189921909
##########
maven-core/src/main/java/org/apache/maven/internal/impl/DefaultArtifactCoordinate.java:
##########
@@ -30,11 +31,11 @@
* A wrapper class around a maven resolver artifact.
*/
public class DefaultArtifactCoordinate implements ArtifactCoordinate {
- private final @Nonnull AbstractSession session;
Review Comment:
Sure! I've just pushed a commit to undo this part.
> 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)
