Maven settings file is ignored and dependencies are not downloaded

Company-specific dependencies from a corporate Nexus are not downloaded.

Environment

• Operating System: Windows
• JDK version: 8
• Visual Studio Code version: 1.79
• Java extension version: 1.20. 1.21 (pre-release)

Steps To Reproduce

1. Load a Maven project with dependencies from a corporate repository specified by a profile in settings.xml file

Current Result

The company-specific dependencies are not loaded

Expected Result

All the dependencies shall be loaded

Additional Informations

In the Output window, following log appears:
CMD :"c:\Users\4637965_software\apache-maven-3.9.1\bin\mvn" --quiet clean -f "c:\Users\4637965_work\projects<project>\pom.xml" && "c:\Users\4637965_software\apache-maven-3.9.1\bin\mvn" --quiet org.apache.maven.plugins:maven-dependency-plugin:3.0.2:tree -f "c:\Users\4637965_work\projects<project>\pom.xml" -DoutputFile="c:\Users\4637965_work\projects<project>\target\dependencies.txt" -DoutputType=dot -DappendOutput=true
STDOUT : [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:3.0.2:tree (default-cli) on project : Cannot build project dependency graph: Could not resolve nor collect following dependencies: []: ...Could not find artifact ... in central (https://repo.maven.apache.org/maven2) -> [Help 1]

It seems like when the project dependency information is read, the settings like java.configuration.maven.globalSettings are not applied at all. Because the settings.xml file is not used in the command mentioned in the logs above.
Maven build works fine, and Microsoft's "Maven for Java" plugin also works just fine. The problem is only with the Java support plugin by RedHat.

Beginne damit, den in den Logs gezeigten Befehl für Abhängigkeitsinformationen und die Art und Weise zu untersuchen, wie er java.configuration.maven.globalSettings und settings.xml liest. Reproduziere die Suche im Abhängigkeitsbaum mit einem unternehmensinternen Maven-Profil; erfolgreich ist die Änderung, wenn die unternehmensinternen Abhängigkeiten aufgelöst werden, statt nur in Maven Central gesucht zu werden.