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.
I create a new class named "TestListModel" , extending "AbstractListModel". First I fixed the imports with "ctrl+shift+i" but forgot the <String> generic, and directly chose "Import all abstract methods". Then I added the <String> generic and got an error. You can chose "Implement all abstract methods" as often as you want everytime a new "getElementAt()"-method will occur and the bug is reproducable anytime.
reproducible
Hm. A simple fix would be to not generate a method iff there is a method with a different signature, but the same erasure. However the produced class would be still incorrect. Possibly more correct behaviour would be to suggest to CHANGE an existing method to match the current type parameters. Or even better, make the hint two-step: first suggest to implement all entirely missing methods, then (as a second step), suggest to change existing methods with mismatched signatures. Requires (probably) also to change the result type throughout the method i.e. whenever unqualified or this.qualified method is called. I'll implement the exclusion first, and keep the rest as an ehnahcement.
Partially implemented as jet-main#16a551c07a02, keeping rest as enhancement issue #251561
Integrated into 'main-silver', will be available in build *201504120001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/16a551c07a02 User: Svata Dedic <sdedic@netbeans.org> Log: #246477: prevented generation of conflicting methods in "implement abstract methods" fix