Bug 545467

Summary: [null] editor shows constrain mismatch due to class annotations
Product: [Eclipse Project] JDT Reporter: Frank Benoit <frank.rene.benoit>
Component: UIAssignee: JDT-UI-Inbox <jdt-ui-inbox>
Status: NEW --- QA Contact:
Severity: normal    
Priority: P3 CC: stephan.herrmann
Version: 4.10   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard: stalebug
Attachments:
Description Flags
Example to reproduce
none
The error shown by the editor none

Description Frank Benoit CLA 2019-03-16 08:23:28 EDT
Created attachment 277901 [details]
Example to reproduce

The attached example shows an interface

public interface Intf {
	public String getSomething();
}

@MessageDecl( values={
		@MessageArgDecl(name=Impl2.FIELDNAME_ID),
})
public class Impl2 implements Intf {
	public static final String FIELDNAME_ID = "Id";
	@Override
	public String getSomething() { // <<--- problem is shown here
		return "";
	}
}

This only happens with the annotations given.
All package are with @NonNullByDefault.
Comment 1 Frank Benoit CLA 2019-03-16 08:24:18 EDT
Created attachment 277902 [details]
The error shown by the editor
Comment 2 Frank Benoit CLA 2019-03-16 08:46:40 EDT
The error shown goes away if the line with @MessageArgDecl is commented out.
Comment 3 Stephan Herrmann CLA 2019-03-16 13:00:25 EDT
Is @NonNullByDefault effective in that code region?
Comment 4 Eclipse Genie CLA 2021-03-06 11:37:41 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 5 Eclipse Genie CLA 2023-03-04 11:12:26 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.