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: | Don't finish a scan before you run the code! | ||
---|---|---|---|
Product: | java | Reporter: | Torbjorn Norbye <tor> |
Component: | Project | Assignee: | Tomas Zezula <tzezula> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | jglick, vstejskal |
Priority: | P2 | ||
Version: | 6.x | ||
Hardware: | PC | ||
OS: | Mac OS X | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Torbjorn Norbye
2010-03-08 20:57:17 UTC
Could you please run the IDE with -J-Dorg.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.level=FINE, reproduce the problem and attach the IDE's log file here? Thanks IIRC this was already filed and marked fixed some time ago - but only if you do not use Compile on Save. If you do use CoS, then running the app will actually use the class files generated during scanning, so naturally you have to wait for this compilation to finish before you can run. Apologies. I can not reproduce now. I run both a lot of Java projects and a lot of JavaFX projects and I was under the impression I was seeing this for both, but now that I've tried to reproduce it deliberately only for Java I can't -- I now suspect it might have been JavaFX projects every time. I've filed a separate issue for JavaFX (issue 181653). It also seems to be more problematic there because class scanning takes quite a bit longer. The problem was fixed when CoS is disabled in NB 6.7 for J2SEProject, see issue #166527. When Compile on Save is enabled, the run has to wait the until scan validates the caches. But JFXActionProvider has similar code without the fix, you probably started a JavaFX app, right? |