20150429 but not a new issue. If I open a pom.xml in the editor and modify it and save, NB correctly reloads the POM definition, and I can see the resulting effects—for example, classpath scanning if I have changed <dependencies>. But there are two common cases where changes are not detected automatically and I need to remember to use Reload POM manually:

· I have a multimodule project where the child modules refer to the parent POM using <parent>. If I change that parent POM, that parent project is updated, but not the children. I would expect that when the MavenProject is loaded that specifies a <parent> using a relative path, NB would listen to changes in that parent pom.xml (and grandparent etc., if applicable).

· I switch Git branches from a shell when an project is not open (but was earlier that day). I then open it in NB. The project definition is still cached from the earlier load. I would expect opening a project to check for changes in the POM.