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.
040616, fresh mdr cache. Just working on a simple j2seproject and trying to use code completion.
Created attachment 15792 [details] Stack trace
BTW this stack trace was preceded by a large number of error messages like [...] error: __input:138,1: illegal character: \35 error: __input:146,17: illegal character: \35 error: __input:149,1: illegal character: \35 error: __input:186,1: illegal character: \35 error: __input:190,1: illegal character: \35 error: __input:192,1: illegal character: \35 error: __input:193,1: illegal character: \35 error: __input:195,1: illegal character: \35 JDK 1.5.0 b55, Linux.
The same exception is thrown over and over whenever I try to do anything in the file, even plain text editing. Fast Import and Fix Imports do nothing, i.e. offer the correct dialogs but make no changes.
Possible factors: 1. Some classes were not imported when the first automatic parse of the file occurred. But after fixing the imports (manually), the error persists. 2. I have more than one copy of JDK sources in my default platform, since I have an XML decl like this: <!-- ... --> <sources> <resource>jar:file:/space/jdk1.5/src.zip!/</resource> <resource>jar:file:/space/src/jdk150b51-solwin-src.zip!/j2se/src/share/classes/</resource> <resource>jar:file:/space/src/jdk150b51-solwin-src.zip!/j2se/src/solaris/classes/</resource> <resource>jar:file:/space/src/jdk150b51-solwin-src.zip!/j2se/src/windows/classes/</resource> </sources> <!-- ... --> and also more than one Java platform registered. This class was initially bound to the default platform.
This bug was already reported this morning and fixed by Tomas Hurka. Strangely the fix got removed by one of my commits. I have no idea how that could happen since I haven't used any CVS tricks, just a regular diff/commit/update (I missed the removal in the diff since it was 2 lines in a lot of changes). I have now reapplied the fix so this issue should now be fixed in trunk.