Rename method of generic type misses one method

[stephan]

Tests #testGenerics1 and #testGeneric3 in org.eclipse.jdt.ui.tests.refactoring.RenameVirtualMethodInClassTests fail to rename one method reference.
See:

• http://www.objectteams.org/distrib/jacks/1.1.6/junit/tests/test-d3e66688-testGenerics1.html
• http://www.objectteams.org/distrib/jacks/1.1.6/junit/tests/test-d3e66696-testGenerics3.html

These refactorings require the RippleMethodFinder2 which has not yet been integrated with the OT/J (needs RegionBasedOTHierarchy).

Disabling these two tests for now.

[jogeb]

The RippleMethodFinder2 works already with the standard OTTypeHierarchy. To get a better support for OT/J programs, the OTHierarchy is used instead of the JDT's RegionBasedHierarchy. The test #test07 in org.eclipse.jdt.ui.tests.refactoring.IntroduceIndirectionTests has to be disabled, because the RippleMethodFinder2 using the OTTypeHierarchy misses one method occurrence.

The other Tests #testGenerics1 and #testGeneric3 can be enabled again.

The development of a RegionBasedOTHierarchy requires the implementation of a new RegionBasedOTHierarchyBuilder. A simple solution that tried to use inheritence like the JDT's RegionBasedHierarchyBuilder did not work, because the OTTypeHierarchyBuilder does not extend the JDT HierarchyBuilder and uses its own build strategy.

[stephan]

After the fix for #330 two tests in IntroduceIndirectionTests toggled behavior:

• test07 now passes (re-enabled)
• test24 now fails (disabled)

[stephan]

This ticket has moved to Eclipse bug 310874 (won't be fixed from objectteams.org)