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: | [68cat] Improve scanning (SoD per project) | ||
|---|---|---|---|
| Product: | java | Reporter: | Peter Nabbefeld <epdv> |
| Component: | Source | Assignee: | issues@performance <issues> |
| Status: | NEW --- | ||
| Severity: | blocker | CC: | mkuchtiak |
| Priority: | P3 | Keywords: | PERFORMANCE |
| Version: | 6.x | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Issue Type: | ENHANCEMENT | Exception Reporter: | |
public abstract boolean shouldScan(FileObject path); not sure if this belongs to performance. thanks. My problem is just, I'm working on sources for a non-J2EE server. Thus, NB does not know, when sources are updated and checks the modification status without necessity :( If I'd implement my own project type and/or actions, I could tell NB when to do scanning - and when not. This is especially important, as the sources are on a mapped device (Windows) :( It would thus help to improve performance significantly, if it would be possible to control scanning. |
[ JDK VERSION : 1.6.* ] Please add an abstract class to be registered in a project's lookup, so a project type (BTW, want to create my own) can decide whether to scan a jar file or classpath. E.g.: public abstract class ProjectIndexingActivityInterceptor { ... public final IndexingActivityInterceptor getGlobalIndexingActivityInterceptor() { ... } public final refreshJarOrFolder(FileObject path) { ... } public abstract shouldScan(FileObject path); }