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.
Build 1152 IE version, Redhat Linux 6.2 with JDK 1.3 Create and select a package. Capture a db schema from a database. Generate java files from dbschema. Compile all, See that compilation is OK. Select the above package and rename it. Compile all, Observe there are some compilation errors. Renaming the package should update all contents in the package
What compilation errors ? Would you please attach the output from the compiler or at least post error messages ? Simply stating that thing does not work does not help at all in getting to the root cause. What are the kinds of files inside the package subtree rooted at the renamed one ? Remember: Updating package statements does _not_ update fully qualified referencies to that package neither does update imports; there is not a project- or system-wide registry of such dependencies and scanning whole Fileystems is not feasible.
It's java module-specific, changing product
Svata, please click "Reassign bug to owner of selected component" when changing Product, to switch the assignee mail address. Is there any reason why Severity is set to Critical? This looks like Normal to me, assuming the sources were simply not updated (and not corrupted). The present behavior of changing the package automatically was added fairly recently and there were not bitter complaints about it before that time.
The severity was unchanged from creation of the report. I have no response/confirmation about what exactly is not updated.
The described behavior is by design. When a package is renamed in the Explorer, only the 'package' declarations of contained files are updated. Imports and fully-qualified type declarations within the files are not changed. As a result, both the contained files and the files with references to them may not be compilable. Although the Java module could probably do a little better job and try to adjust the declarations in the contained files, it cannot update the other files that may also include reference to the old package structure. I'm changing the priority to P5 and set the sererity to 'enhancement'.
Target milestone -> 3.3
Target milestone -> 3.3.1.
Cleaning up before 4.0 planning
Target milestone was changed from not determined to TBD
*** Issue 11229 has been marked as a duplicate of this issue. ***
Fixed by refactoring module.