-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ctrl+click no longer opens the pom on maven dependencies. #1607
Comments
I tried it and I cannot reproduce the described behavior. |
Lemminx-maven has changed the path to store the dependencies resolved during the build in order to not pollute the main maven repository with the temp artifact folders which are created on "as-you-type" builds. Building a maven artifacts while editing a .. which pollutes the repository with the unwanted data and may lead to different problems with maven builds. So now, everything resolved/installed by maven goes to the maven repository (which is now used as read-only for lemminx-maven), while everything build during the editing goes to that And it's expected if some artifact @cnoel35 if you believe that the file opened by |
Ok, thanks for your responses, I will open an issue in lemminx-maven github. |
Here the issue I opened into lemminx-maven : eclipse/lemminx-maven#531 |
Still a problem in 2023-12 |
On Eclipse 2023-09, a Ctrl+Click on a pom dependency no longer opens the dependency pom but a file without extension present in the
.m2\.lemminx-maven\
folder (what is that lemminx folder ??).On the same project with eclipse 2022-06 (without this lemminx folder) it works perfectly and opens the corresponding pom.
System information
M2E - POM Editor using LemMinX language server (includes Incubating components)
2.0.5.20230815-1219
Eclipse IDE for Enterprise Java and Web Developers (includes Incubating components)
Version: 2023-09 (4.29.0)
Build id: 20230907-1323
Eclipse Adoptium
jdk-17.0.6.10-hotspot
Windows 10 Version 22H2
build 19045.3570
The text was updated successfully, but these errors were encountered: