Bugzilla – Full Text Bug Listing
| Summary: | Extract to method refactoring creates method with redundant nullness annotation warning | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Gunnar Wagenknecht <gunnar> |
| Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 4.7 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | stalebug | ||
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. |
- package with DefaultNonNull annotation - select expression and invoke "Extract to method" - new method is generated as: private static @NonNull ... ...() {...} The generated code shows a warning "The nullness annotation is redundant with a default that applies to this location". A quickfix is available to remove the warning. I think Eclipse should not generate this annotation if it's clear that it would be redundant.