Mossroy created NETBEANS-4656:
---------------------------------
Summary: Regression : Maven dependencies are not always refreshed
Key: NETBEANS-4656
URL: https://issues.apache.org/jira/browse/NETBEANS-4656
Project: NetBeans
Issue Type: Bug
Components: projects - Maven
Affects Versions: 12.0
Environment: Reproduced on 2 platforms :
Windows 8.1, Java 11, Maven 3.3.9
Ubuntu 20.04, Java 11, Maven 3.3.9
Reporter: Mossroy
With a Maven project, if you define a dependency version in a property of a
parent module, changing this property in the parent module does not update the
dependencies in the GUI of the submodule. You need to restart Netbeans for this
change to be visible.
It was working fine in Netbeans 11.0.
Steps to reproduce :
* clone the test-case I uploaded on
[https://gitlab.com/mossroy/test-case-netbeans-maven-dependency-versions]
* open it and build it with Netbeans 12
* in the "projects" tab of Netbeans, open the child module, and see the
"dependencies" : there should be spring-core-5.2.8.RELEASE
* in the pom.xml of the parent module, change the spring.version property to
5.2.7.RELEASE
* in the child module, in "dependencies", 5.2.8.RELEASE is still displayed. It
should have been changed to 5.2.7.RELEASE
If the property is moved in the child module, it works fine.
Workaround : restart NetBeans. Reloading the project is unfortunately not
enough.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
