Skip to content
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

properties not resolved after changing POM and rebuilding #541

Closed
eliasbalasis opened this issue Jan 9, 2024 · 1 comment
Closed

properties not resolved after changing POM and rebuilding #541

eliasbalasis opened this issue Jan 9, 2024 · 1 comment

Comments

@eliasbalasis
Copy link

eliasbalasis commented Jan 9, 2024

In Eclipse 2023-09 with latest m2e 2.4.0 installed which still carries lemminx-maven 0.10.1 but seems to be fixing #513:

When making changes to a POM a build is automatically triggered but the Maven properties sometimes are not resolved and wrong values are assigned in *.properties files

I guess this could be either a lemminx issue or a M2E Core one, but given #540 I am guessing it could be lemminx related.

@mickaelistria
Copy link
Contributor

I think this one is more about m2e: lemminx doesn't execute the mojos, it doesn't generate the *.properties file, it just reads poms to display info in editor. So if the issue happens in the build more than in the editor, it's most likely m2e.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants