AbstractRefactoring AssertionError on Find Usages

context

• Clicked on 'Find usages' ALT/F7
• Symbol is a @Override of a library method
• Find Usages dialogue popped up
• Press [*Find*]

expected / desirable

• Expected netbeans to run-off and find usages

actual

• Instead received a "Review and Report Problem" error
  • AssertionError from refactoring code (see stack trace attached)
• Disclaimer about how finding library methods wasn't foolproof
• Pressed [*Find*]
• Received another pop-up with an AssertionError from Annotation-s
• Needless to say NO instances of the target method were listed in the Usages window.

Impact

• With Netbeans 8.2 some method occurrences are found
• I certainly don't see Assertion Errors
• It becomes annoying to just have to cancel error reports
• The ALT/F7, 'Find Usages' command is one of the major commands used
  • I don't recall the Eclipse command but Ntebeans and IDEA teams I've worked on ALT-F7 was a common catch cry
  • If you want flexible and responsive development, Refactoring and Test support are #1 priority.
• Speaking personally I don't understand the large number of Regression errors I'm seeing.
  • Before my PC crashed I was working hard to find significant errors in Netbeans 8-beta.

supporting information

• messages.log
• AbstractRefactoring-AssertionError.logs, contains ...
  • UI log
  • IDE log
  • stacktrace
• Annotation-AssertionError.logs
  • UI log
  • IDE log
  • stacktrace