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: | Compile on save and F6 | ||
---|---|---|---|
Product: | java | Reporter: | fommil <fommil> |
Component: | Compiler | Assignee: | Dusan Balek <dbalek> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | ||
Priority: | P3 | ||
Version: | 7.2 | ||
Hardware: | PC | ||
OS: | Mac OS X | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
fommil
2012-08-05 11:31:08 UTC
Unfortunately, I cannot reproduce the problem. Could you please create a simple reproducible test case (simple project + exact steps to reproduce) and attach it to the issue? Thanks. Bizarre, it seems to have fixed itself. But I swear this *was* happening yesterday. Is there any way for me to *absolutely guarantee* that "build" is called prior to a run? That way I can at least blame Maven if the classes aren't recompiled. not fixed - back again - and not just in JFrame. It is erratic and I can't create a standalone test. As a workaround, is there any way to ensure that F6 calls "compile" before "run". Ideally, it would delete any "jar" that has been built. When I hit F6, I can drop to the terminal and "mvn compile" will update the binaries because Netbeans isn't compiling the files. Workaround: completely disable "compile on save" and the F6 etc commands will then invoke the correct Maven compilations. Report from old NetBeans version. Due to code changes since it was reported likely not reproducible now. Feel free to reopen if happens in 8.0.2 or 8.1. |