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.
[Netbeans 200410202002; JDS v.2; JDK 1.5.0_01-b04] I have the following code: private void methodA(int i) { } protected void methodA(int i, String text) { } When I try to change method parameters for the first method, I am allowed to add a parameter of type String. Thus I end up with having: private void methodA(int i, String text) { } protected void methodA(int i, String text) { } Which my compiler doesn't like so much. I can also add this parameter if both methods are protected. P2 because according to Marek this already used to work, so it is a regression.
Marek is right, this already used to work.
Seems that new parameter type is not resolved and that is the reason why it does not clashes with other method because unresolved type cannot be compared with any other type.
Hm, so it is not a regression. I found out that it works correctly for primitive types or fully qualified names. For simple names it never works. So as a workaround you can use fully qualified names. (I know that it is annoying and we need to solve it, unfortunately there is no direct solution for it. We need to expose resolving of simple names outside the parser and put it to the API. Changing to ENHANCEMENT.
Yes, you're right. I've tried to use "java.lang.String" and that works pretty fine. Perhaps this could be mentioned somewhere in relnotes in 4.0 for case that people would complain that refactoring broke their code.
Changed TM from 4.1 to TBD, please re-evaluate. Thanks!
Different architecture used. This will not be fixed.