Bug 374043 - make static fields final throughout JDT/Core
Summary: make static fields final throughout JDT/Core
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.8   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-13 05:06 EDT by Stephan Herrmann CLA
Modified: 2022-09-18 16:56 EDT (History)
2 users (show)

See Also:

Attachments
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 Stephan Herrmann CLA 2012-03-13 05:06:10 EDT 
Bug 372319 comment 55 has a list of static non-final fields in JDT/Core.
All of these fields are suspects for sharing state which could cause concurrency issues.

We should go through the list and make final as many of these fields as possible.
Comment 1 Srikanth Sankaran CLA 2012-03-20 11:33:24 EDT 
If you plan to include a fix for this in 3.8 M7, please adjust the
target suitably, so it becomes easier to track.
Comment 2 Eclipse Genie CLA 2019-07-28 10:21:13 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 Stephan Herrmann CLA 2019-07-28 13:02:53 EDT 
still relevant but not scheduled.

For easier reference, here's the list of non-final static fields from back then: attachment 212432 [details]
Comment 4 Eclipse Genie CLA 2022-09-18 16:56:15 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.