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.
Summary: | Do not fire ClassPath changes after project reload unless necessary | ||
---|---|---|---|
Product: | projects | Reporter: | pekarna <pekarna> |
Component: | Maven | Assignee: | Jesse Glick <jglick> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | Keywords: | PERFORMANCE |
Priority: | P3 | ||
Version: | 7.1 | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 206445 |
Description
pekarna
2011-12-22 04:58:24 UTC
If pom.xml is edited, the MavenProject has to be reloaded; trying to determine the kind of text edited would be far too difficult and unreliable, changes to some non-classpath metadata such as <name> still need to be recognized, and project loading is usually quick anyway. But reloading the project should not trigger change events in various query results (e.g. ClassPath) unless the classpath actually changed as a result of your edit (e.g. you added a <dependency>). And that is in fact exactly the behavior I observe: if I make a real change to dependencies, the log file records a rescan as expected; if I edit some comments in the POM, nothing of the sort happens. If this is not what you see, then I need steps to reproduce. |