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.

Bug 46107 - Using JDK 1.5 enum in annotation definition causes NPE
Summary: Using JDK 1.5 enum in annotation definition causes NPE
Status: VERIFIED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 4.x
Hardware: PC Linux
: P2 blocker (vote)
Assignee: _ tball
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-07-13 16:45 UTC by dkkopp
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Java source of annotation (732 bytes, text/plain)
2004-07-13 16:47 UTC, dkkopp
Details

Note You need to log in before you can comment on or make changes to this bug.
Description dkkopp 2004-07-13 16:45:38 UTC
I am using the July 12 daily build. If I try to
define an enum inside of the annotation
definition, the editor starts throwing NPEs. The
stack trace shows the MDR package, so I filed the
bug against MDR.

I will attach the file. Please note that you can
use an enum defined in another place without any
problem.
Comment 1 dkkopp 2004-07-13 16:47:17 UTC
Created attachment 16227 [details]
Java source of annotation
Comment 2 dkkopp 2004-07-13 16:49:59 UTC
Actually, looking at the stack trace a little more carefully, this may
actually be a bug in the java parser in javacore.
Comment 3 Martin Matula 2004-07-14 09:26:07 UTC
Reassigning to javacore.
Comment 4 Pavel Flaska 2004-07-15 15:39:48 UTC
It is caused by semicolon at the end of enum declaration. It is a bug
in gjast. Semicolon is reported as ASTree.BLOCK_STATEMENTS.
Reassigning to Tom.
Comment 5 _ tball 2004-07-16 00:01:38 UTC
Block fixup used in classes and enums wasn't being called when
creating annotation definitions.
Comment 6 Jiri Prox 2005-07-11 14:10:13 UTC
Verified in 4.2 (200507110943)
Comment 7 Quality Engineering 2007-09-20 09:51:47 UTC
Reorganization of java component