Bug 541608 - [null] unhelpful/wrong non-null annotation inherited method diagnosis
Summary: [null] unhelpful/wrong non-null annotation inherited method diagnosis
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.10   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-27 10:52 EST by Ed Willink CLA
Modified: 2023-02-10 10:59 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ed Willink CLA 2018-11-27 10:52:39 EST
I have been struggling for many months to solve:

  Missing non-null annotation: inherited method from Set<E> specifies this parameter as @NonNull

which occurs on the org.eclipse.ocl.pivot.internal.values.OrderedSetImpl of 

  public class OrderedSetImpl<E> extends LinkedHashSet<E> implements OrderedSet<E>

I have eventually tracked the problem to an external annotation for Collection.addAll enforcing a non-null argument, but no corresponding annotation for AbstractCollection.addAll.

When I add the extra annotation to make AbstractCollection 'consistent' the problematic message on OrderedSetImpl goes away.

We therefore have multiple problems.

Primarily that the diagnostic gives no clue as to the actual method (addAll) or classes (Collection/AbstractCollection) that are causing JDT a difficulty.

Additionally, surely AbstractCollection should inherit rather than conflict with the Collection external annotation?
Comment 1 Eclipse Genie CLA 2020-11-17 07:53:50 EST
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 2 Eclipse Genie CLA 2023-02-10 10:59:11 EST
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.