-
Notifications
You must be signed in to change notification settings - Fork 31
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
Doesn't support properties defined in .mvn/maven.config
#549
Comments
I also noticed this today, this is quite annoying, any hints where properties are evaluated so one can probably suggest a fix? |
Best is to have a look at Maven code and look for how |
Well this happens as part of MavenCLI, m2e already supports it I just don't know how this could / should be applied to lemminx, e.g you can look at it extracts the data from the maven config given the Multi Module Directory is known like here: it would be great if this could be fixed because currently users blame this on m2e even though it actually supports this and it is a language server error... |
Just to not set false expectation: neither Victor nor I are very active on this project at the moment, so it's not likely we try to fix it soon. But as usual, we try to make reviews of incoming PRs highest priority ;) |
Wel my problem is that I'm not very familiar with the codebase, but you knwo m2e as well, so maybe you can point me to where something similar like the |
I also looked a bit into this a while ago and I assumed one could start in m2e's InitializationOptionsProvider to feed the language server with the corresponding properties. |
This one seems only called once and on config change but not for pom files I open with the editor, as each |
Currently lemminx does not consider properties that are defined in the .mvn/maven.config and therefore gives errors or otherwhise wrong results when parsing a project. This adds support for detecting and reading these properties from the .mvn/maven.config Fix eclipse-lemminx#549 Signed-off-by: Christoph Läubrich <laeubi@laeubi-soft.de>
@mickaelistria I started a very basic implementation here: I have not tested this yet but found already some uncertainties, I added |
Currently lemminx does not consider properties that are defined in the .mvn/maven.config and therefore gives errors or otherwhise wrong results when parsing a project. This adds support for detecting and reading these properties from the .mvn/maven.config Fix eclipse-lemminx#549 Signed-off-by: Christoph Läubrich <laeubi@laeubi-soft.de>
Currently lemminx does not consider properties that are defined in the .mvn/maven.config and therefore gives errors or otherwhise wrong results when parsing a project. This adds support for detecting and reading these properties from the .mvn/maven.config Fix #549 Signed-off-by: Christoph Läubrich <laeubi@laeubi-soft.de>
To create a new structured build/pomless Tycho build for an Eclipse plugin, I have been instructed to look at https://tycho.eclipseprojects.io/doc/4.0.5/StructuredBuild.html, but it seems
.mvn/maven.config
that I'm instructed to create for this is not being picked up by this plugin and as such I get:When opening the pom.xml in Eclipse.
See also eclipse-tycho/tycho#3481 (comment)
The text was updated successfully, but these errors were encountered: