Bug 385919 - [warnings] Empty block warning should not be triggered for class bodies
Summary: [warnings] Empty block warning should not be triggered for class bodies
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.8   Edit
Hardware: PC Mac OS X
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-25 05:04 EDT by Sebastian Zarnekow CLA
Modified: 2022-05-28 00:41 EDT (History)
0 users

See Also:

Attachments
Screenshot (9.56 KB, image/png)
2012-08-06 09:33 EDT, Tomasz Zarna CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sebastian Zarnekow CLA 2012-07-25 05:04:02 EDT 
I don't expect a warning for empty class bodies, e.g. like the following:

abstract class MyMeaningfulName implements Callable<String> {
}

Same for things like Guavas idom new TypeLiteral<List<String>>() {}
Comment 1 Tomasz Zarna CLA 2012-08-06 09:33:46 EDT 
Created attachment 219591 [details]
Screenshot

I can see no warning in I20120805-2000.
Comment 2 Eclipse Genie CLA 2020-06-04 14:49:08 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.

If you have further information on the current state of the bug, please add it. 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.
Comment 3 Eclipse Genie CLA 2022-05-28 00:41:30 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.

If you have further information on the current state of the bug, please add it. 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.