change of property value in ancestor module is not reflected in descendant module unless a new XML Language server is started

[eliasbalasis]

In Eclipse 2023-12

when the of a Maven property that is inherited from an ancestor module changes,
hovering over a reference to the changed property in a descendant module,
displays the old value.

If a new XML Language Server is started, the new value is displayed.

[mickaelistria]

I think it may depend on the project layout, what is imported as a project in the IDE and what's not imported. In general, Lemminx-Maven doesn't monitor the whole pom hierarchy to trigger re-resolution of pom (and I think it should).
Can you please provide a minimal test case to reproduce with Eclipse m2e? We could then try to convert it into a test-case for lemminx.

[eliasbalasis]

I have a structure for testing Maven editor behaviors (see #345)

https://github.com/eliasbalasis/eclipse-lemminx-maven-issue-345-root
https://github.com/eliasbalasis/eclipse-lemminx-maven-issue-345-tools

Import these into an Eclipse workspace in the order mentioned and experiment with the value of property net.upperlimit.root.property1 on the first project in relation to property net.upperlimit.root.property1.ref on the second project.

Changing the value on the first project does not display the new value on the second project,
until a new XML Language server is started.