Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 419727

Summary: [compiler] Compiler should not generate "problem types" for annotation types.
Product: [Eclipse Project] JDT Reporter: Markus Keller <markus.kell.r>
Component: CoreAssignee: ANIRBAN CHAKRABORTY <anchakrk>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: manoj.palat, srikanth_sankaran
Version: 4.3   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard: stalebug

Description Markus Keller CLA 2013-10-17 11:00:24 EDT
BETA_JAVA8

Create this annotation type with an illegally empty argument list for @Target:


package jsr308.invalid;

import java.lang.annotation.Target;

@Target()
@interface Ann {}


=> Log entry:
!ENTRY org.eclipse.jdt.core 2 0 2013-10-17 16:55:00.198
!MESSAGE The Java indexing could not index /zz1.8/bin/jsr308/invalid/Ann.class. This .class file doesn't follow the class file format specification. Please report this issue against the .class file vendor
Comment 1 Srikanth Sankaran CLA 2013-11-14 22:53:44 EST
It is wrong to create a "problem type" for annotation types with errors.
They don't have a clinit or init or actual method bodies to emit the
exception throwing code into.

Fix should be trivial. Just short circuit problem type generation for
annotation types.

A test could then simply assert for file's non-existence.

I am removing the [1.8] tag as this has nothing to do with 1.8.

Anirban, since you have a couple of other items to deal with problem methods/types
I'll reassign this to you.
Comment 2 Eclipse Genie CLA 2020-04-03 17:44:32 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.