Bug 530978

Summary: [null] Add @Nullable annotations to jdt core dom API
Product: [Eclipse Project] JDT Reporter: Jean-Noel Rouvignac <djanoiup>
Component: CoreAssignee: JDT-Core-Inbox <jdt-core-inbox>
Status: REOPENED --- QA Contact:
Severity: normal    
Priority: P3 CC: stephan.herrmann
Version: 4.8   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard: stalebug
Attachments:
Description Flags
Add the @Nullable annotation none

Description Jean-Noel Rouvignac CLA 2018-02-09 17:36:00 EST
Created attachment 272622 [details]
Add the @Nullable annotation

It is all too easy to forget adding null-checks after calling the many methods possibly returning null in the JDT core dom API.

Adding @Nullable annotations and enabling compiler warnings in consumer projects would allow catching these simple mistakes right when the code is written.
Comment 1 Eclipse Genie CLA 2020-05-16 11:55:58 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.
Comment 2 Stephan Herrmann CLA 2020-05-16 16:41:38 EDT
.
Comment 3 Eclipse Genie CLA 2022-05-08 17:53:09 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 4 Eclipse Genie CLA 2024-04-28 05:18:37 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.