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: | Different include/exclude sets of a source tree do not trigger rescan | ||
---|---|---|---|
Product: | java | Reporter: | Jesse Glick <jglick> |
Component: | Source | Assignee: | Jan Jancura <jjancura> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | ||
Priority: | P4 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 97168, 98266 |
Description
Jesse Glick
2007-03-19 22:46:04 UTC
In the point (0) it should be enough to close the first project. The problem is that RepositoryUpdater maintains the set of already scanned roots and the root of the old project is the same as a root of the new project => the RepositoryUpdater do not scan it again. For now I don't know any fast way how to find out that the root has different excludes, maybe ClassPath.SOURCE(oldRoot) != ClassPath.SOURCE (newRoot) will work. If it works it will behave like point (2). Old TM. -> 6.0. moving opened issues from TM <= 6.1 to TM=Dev Two projects on the same source root are not supported, but on the other side the implementation described by Jesse in point (1) should be doable and may help. Resolving all issues with milestone "future" as LATER. If you feel strongly that it should be implemented please reopen and set the target milestone to "next". NetBeans.org Migration: changing resolution from LATER to WONTFIX |