16 duplicate so far ... only on Vista & XP
Build: NetBeans IDE 6.5 Beta (Build 200808111757)
VM: Java HotSpot(TM) Client VM, 1.5.0_13-119, Java(TM) 2 Runtime Environment, Standard Edition, 1.5.0_13-b05-237
OS: Mac OS X, 10.5.4, i386
STACKTRACE: (first 10 lines)
com.sun.tools.javac.util.FatalError: Fatal Error: Unable to find method initCause
Seems like a source level is set to 1.5/1.4 while compiling against 1.4/1.3 or lower libraries.
changeset d454571df68f in main
*** Issue 152406 has been marked as a duplicate of this issue. ***
*** Issue 155012 has been marked as a duplicate of this issue. ***
Integrated into 'main-golden', will be available in build *200901070201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
User: Dusan Balek <email@example.com>
Log: Issue #151422: com.sun.tools.javac.util.FatalError: Fatal Error: Unable to find method initCause - fixed.
haven't seen new report since fix was integrated - verified
need to be integrated together with issue 143923
during backport to release65_fixes please change logging level from warning to fine.
The changeset d454571df68f changes the file JavacParser.java but the file JavacParser.java doesn't occur in the release65_fixes nor the release65 branch. It
seems, the file has been merged into the trunk after the NetBeans IDE 6.5 release as a part of significant improvement. If so, the port to the release65_fixes
branch could be non-trivial.
The file JavacParser.java is part of the new java parsing API which was introduced after NetBeans 6.5 IDE release. This is a not suitable candidate for the
Removed from a patch after discussion with QA.
It occurs also on Mac OS X. I was working on a Jdk 1.4 project at that time.
Looks like it's back again - present in 09/02/XX and 09/03/XX builds.
changeset 4c07517dbd79 in main/nb-javac
changeset 2ed03cda8e85 in main-silver
*** Issue 141521 has been marked as a duplicate of this issue. ***
Similar exception just thrown in dev build (see exception reporter - claims it will open a new bug). Seems to be some problem with Enum.valueOf in JDK sources.