Community
Participate
Working Groups
Created attachment 287047 [details] Repro project The attached project demonstrates a refactoring corruption. When Element.java is dragged and dropped from x.y.z1 to x.y.z3, Reference.java is corrupted from: List<@NonNull Element> list; to List<x.y.z3.Element> list; Seems like some bit of code cannot cope with the horrors of of qualified name annotations. Else there is a false assumption that @NonNullByDefault is in use. I never use it. This bug has been present for a few years. I've only just got round to reporting it. Reproducible on RC1 Version: 2021-09 (4.21) Build id: I20210825-1800 ---- (And after the DND, Ctrl-Z reports cannot be undone.)
I don't think this bug has anything to do with null analysis but just the handling of TYPE_USE annotations in generics as I just reproduced it with a dummy TYPE_USE annotation. Basically the title should be: "TYPE_USE annotations on generic type parameters are dropped on refactoring"
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.
