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.

Bug 62549 - Changing method params treated as error
Summary: Changing method params treated as error
Status: RESOLVED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 5.x
Hardware: All All
: P4 blocker (vote)
Assignee: Jan Lahoda
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-18 09:56 UTC by Milan Kubec
Modified: 2009-02-19 21:08 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
screenshot1 (9.33 KB, image/png)
2005-08-18 09:56 UTC, Milan Kubec
Details
screenshot2 (9.20 KB, image/png)
2005-08-18 09:57 UTC, Milan Kubec
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Milan Kubec 2005-08-18 09:56:18 UTC
[dev-200508171800, JDK 1.5.0_04]
Changing method parameters is treated as error.

Steps to reproduce:
1) Have folowing two classes:

public class NewClass {    
    public NewClass() {
    }    
    public void setIt(String s) {
    }    
}
---
public class NewClass2 {    
    public NewClass2() {
        NewClass nc = new NewClass();
        nc.setIt("asdf");
    }    
}

2) Change method parameters of setIt() method in NewClass using refactoring -
add boolean param 'b' with default value 'true'.
3) Finish refactoring
4) Open NewClass2 and see attached screenshot of the wrong error
Then when I try to proceed with the hint which offers me to create the "not
existing" method I end up with broken class as shown on the second attached
screenshot.
Comment 1 Milan Kubec 2005-08-18 09:56:46 UTC
Created attachment 24019 [details]
screenshot1
Comment 2 Milan Kubec 2005-08-18 09:57:20 UTC
Created attachment 24020 [details]
screenshot2
Comment 3 Milan Kubec 2005-08-18 09:59:24 UTC
I could get rid of the error annotation only after rebuilding the project.
Comment 4 Milan Kubec 2005-08-18 10:25:43 UTC
This issue is only reproducible when having those classes with no package
declaration while source files are placed in some package, but it's not illegal.
Comment 5 Jan Lahoda 2008-11-19 12:30:21 UTC
MDR related.