pom.xml reports non-resolvable parent POM error despite local repository having dependencies and IntelliJ IDEA resolving correctly

When using the redhat-developer vscode-java extension in VSCode, I encounter errors in my pom.xml indicating that the parent POM cannot be resolved or dependencies are missing. However, the local Maven repository already contains the required artifacts, and opening the same project in IntelliJ IDEA works perfectly without any errors.
Interestingly, even in VSCode, the reported parent POM is clickable and can be opened normally, despite the error being displayed.
However, inside Java source files, classes, methods, and variables cannot be navigated (Go to Definition does not work), which suggests the Java project classpath is not being built correctly.

Details

• Error message example:
  Non-resolvable parent POM for ...
• Dependencies are present in the local Maven repository and not missing
• IntelliJ IDEA correctly resolves the parent POM and dependencies without issues
• VSCode plugin might not be correctly loading the custom settings.xml or there could be caching issues
• "java.maven.downloadSources": true setting does not seem to take effect; source code is not downloaded
• Maven version 3.6.3 is installed at /Users/yuxuan/SoftWare/maven/apache-maven-3.6.3/bin/mvn on macOS

Relevant settings.json snippet

{
  "java.maven.downloadSources": true,
  "maven.executable.path": "/Users/yuxuan/SoftWare/maven/apache-maven-3.6.3/bin/mvn",
  "java.configuration.maven.userSettings": "/Users/yuxuan/SoftWare/maven/apache-maven-3.6.3/conf/settings.xml"
}

Expected behavior
The plugin should correctly recognize existing dependencies in the local Maven repository without throwing resolution errors

It should properly load and apply the user-specified settings.xml

Source downloading should work as configured

Provide more detailed logs or diagnostics to help troubleshoot issues

Thank you for your hard work and support. Looking forward to a fix.

Start by reproducing the dependency and source-navigation failures in VSCode using the provided settings.json values, the project's pom.xml, and the specified Maven executable. Inspect the extension's detailed logs and diagnostics to determine whether settings.xml loading or dependency caching is involved. Done means existing local dependencies resolve, source downloading follows the setting, and Java navigation works without errors.