Community
Participate
Working Groups
HEAD BinaryMethod#getParameterNames() should not try to extract names from attached javadoc for synthetic methods. By construction, synthetic methods have no javadoc. An exception could be bridge methods, which could use the parameter names of their original method. But I think even there, generated parameter names make it more clear that those methods are compiler-generated. Steps to reproduce: - run HEAD with a VM that makes your firewall show an alert when accessing untrusted internet servers - open java.util.Collections from an 1.5 rt.jar - in the Outline view, select access$000(Object, Object)
Created attachment 58935 [details] Proposed fix
Added regression test org.eclipse.jdt.core.tests.model.AttachedJavadocTests#test022. This test ensures that the parameter names are arg0 and arg1, but it cannot check if there is a connection to the javadoc. This needs to be tested manually following steps described in comment 0. Released for 3.3M6.
Verified for 3.3 M6 using build I20070320-0010