Bugzilla – Full Text Bug Listing
| Summary: | [1.8][null] Bogus error only on incremental build (not on project clean) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Holger Klene <h.klene> | ||||||
| Component: | Core | Assignee: | Stephan Herrmann <stephan.herrmann> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | srikanth_sankaran, stephan.herrmann | ||||||
| Version: | 4.5 | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | stalebug | ||||||||
| Attachments: |
|
||||||||
Created attachment 245589 [details]
zipped workspace
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. |
Created attachment 245588 [details] screenshot Adding a space to NCuser.java and pressing Ctrl+S creates Error: Null constraint mismatch: The type '@NonNull Integer' is not a valid substitute for the type parameter '@NonNull T extends @NonNull Comparable<@NonNull ? super @NonNull T>' Running Project > Clean... will remove that error Also adding a space to both files NaturalComparator.java and NCuser.java with pressing Ctrl+Shift+S (to save both at the same time) will remove that error. this is: eclipse-SDK-N20140730-2000-linux-gtk-x86_64.tar.gz PS: I've read quite some bugs over the past days and somehow I remember another bug with two files and an error vanishing when the usage code was moved into the file of definition. But I cannot find it anymore. There was something about reading a class file back versus freshly compiling from source ...