[pom editor question] How does the pom editor resolve the local repository to analyze dependencies?

[rhoehener]

I ran maven in the cmd prompt once with a custom local repo parameter (-Dmaven.repo.local=reactor-repo), and now the m2e pom editor also uses that repo for dependency analysis and navigation. I get many warnings that plugins cannot be found.

Sometimes I use a custom user settings file in the maven settings to point to (yet another) custom local repo, but currently I have no special configuration (see screenshot).

I tried search for 'reactor-repo' in the eclipse workspace and plugin folders but didn't find anything.

Could you help me debug how m2e resolves the local repository?

[laeubi]

Have you tried "update maven project" with the force option?

[rhoehener]

Yes, this is always the first thing I do: Restart eclipse, then select all projects and update maven projects with force update snapshots.

[rhoehener]

I have also tried deleting all .lemminx-maven folders I could find. It looks to me as if m2e keeps it's own repository there? It looks like it creates that folder next to wherever the 'currently identified local repository' is.

[rhoehener]

I tried to reproduce it with a simple new workspace but no luck so far. But all my real big workspaces are messed up as soon as I start switching between custom user settings and different local repos.

It would already help a lot if I could find the place where m2e stores the location of the local repository (I assume it is some kind of stale cache).

[mickaelistria]

The LemMinX Language Server and its extension for Maven get informed of the path to settings file configured via preferences during their initialization, see

m2e-core/org.eclipse.m2e.editor.lemminx/src/org/eclipse/m2e/editor/lemminx/InitializationOptionsProvider.java

Line 29 in a1dad44

Optional.ofNullable(config.getGlobalSettingsFile()).ifPresent(globalSettings -> mavenSettings.put("globalSettings", globalSettings));

.
The LemMinX extension is supposed to receive it and process it, in org.eclipse.lemminx.extensions.maven.MavenLemminxExtension.initMavenRequest() .

If you want to debug the running language server, please see https://github.com/eclipse-wildwebdeveloper/wildwebdeveloper/blob/master/TIPS_and_FAQ.md#attach-a-debugger-to-the-xml-language-server-process

[rhoehener]

Thank you Mickael, I will have a look!

[rhoehener]

I figured out the reason for the "plugin could not be resolved" warning. The cause is given as "Failed to parse plugin descriptor for ...", followed by a workspace project path (not a local repo path). So I guess the POM editor tries to use workspace resolution to read <plugin-project>/src/main/resources/META-INF/maven/plugin.xml (or the corresponding location in the target dir), which does not exist (generated during packaging and only exists in the final plugin jar).

My current workarounds are:

• close the plugin project -> reopen the pom.xml -> pom editor resolves correctly from local repo (no warnings, goal autocompletion works)
• or bump the plugin-project-version to something different than the plugin-version referenced in all the other workspace projects