This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 252400

Summary: POM changes not reliably picked up
Product: projects Reporter: Jesse Glick <jglick>
Component: MavenAssignee: Tomas Stupka <tstupka>
Status: RESOLVED FIXED    
Severity: normal    
Priority: P3    
Version: 8.1   
Hardware: PC   
OS: Linux   
Issue Type: DEFECT Exception Reporter:

Description Jesse Glick 2015-05-14 10:58:50 UTC 
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.
Comment 1 Tomas Stupka 2015-06-12 15:34:52 UTC 
fixed in jet-main #5bbce67793b9
Comment 2 Quality Engineering 2015-06-13 07:20:55 UTC 
Integrated into 'main-silver', will be available in build *201506130001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)

Changeset: http://hg.netbeans.org/main-silver/rev/5bbce67793b9
User: Tomas Stupka <tstupka@netbeans.org>
Log: Issue #252400 - POM changes not reliably picked up