This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Example: Given interface X { void a(); void b(); } interface Y extends X { void c(); void d(); } for "new Y() { }" the method implementations are generated in the order c, d, a, b. The expected, more intuitive and useful order would be a, b, c, d. Basically post-order rather than pre-order when traversing the super-type tree.
PS: This should also remain true with return type specialization. I have use cases like interface X { Number f(Number a, Number b); Number f(Number a, Integer b); Number f(Integer a, Number b); Number f(Integer a, Integer b); } interface Y extends X { Integer f(Integer a, Integer b); // specialize return type } where for implementations of Y the method implementations are then generated in the order Integer f(Integer a, Integer b); Number f(Number a, Number b); Number f(Number a, Integer b); Number f(Integer a, Number b); which is annoying not only because the parameter combinations are not properly "sorted" any more, but also because it's inconsistent with the order generated for implementations of X, which leads to confusing the methods when switching between the source code of the different implementations.
I think this is either P3 enhancement request or P5 bug depending on how you look at the behaviour.
implemented as hint
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue. Thanks for your cooperation, NetBeans IDE 8.2 Release Boss
Still reproducable in current dev build.