Issue resolving imports and artifacts since today... anyone else?

[abenz1267]

Hello,

i'm not sure if that's only me and my system rn, but i'm getting errors with some imports and artifacts today.

• VSCode works fine
• building locally via maven works fine as well

It's definitely not a problem with the project itself. I can't figure out why i'm getting those errors out of a sudden.

Anyone else? Stable nvim, plugins all up-to-date.

Regards

[abenz1267]

This doesn't happen on my second machine, same config.

[vishal423]

I see. I assume you are using correct jdt runtime. If you could share error screenshots related to imports, then, it may help diagnose the issue?

[abenz1267]

Sorry, i'm at the office again next monday. But it's just generic "unresolved import"-kinda errors. And maven artifact errors. But yeah... it builds and runs fine on VSCode on that machine. On my current machine: no problem at all. I'm lost. :D

[abenz1267]

Finally back at work. So what i did now:

• updated my system (Arch)
• removed .m2 folder
• removed workspace folder
• reinstalled all LSPs and nvim plugins
• did a maven clean

Errors are still present: The import *redacted* cannot be resolved. The file is literally present in the project though.

I don't understand why I'm getting those issues on this machine, but not on my other one. Same configuration.

Edit: When jdtls was initializing, it was missing a lot of artifacts... but running mvn clean should have installed all those, or not?

[abenz1267]

It complains about missing artifacts that are definitely present in my .m2 folder. Otherwise building with maven from cmd-line wouldn't work...

[abenz1267]

Ok, i've fixed the issue by copying my /usr/share/java/maven/conf/settings.xml into ~/.m2.