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.
What happens when you try to refactor a class that impacts other classes? In theory it should check out all the files. But then: what happens if some files a already checked out as reserved by other people? My proposition is to open warning dialog where the user could choose between dismissing the refactoring or check out as "unreserved" the files that are reserved. But please absolutely avoid modifying half the files (this happened with VSS generics and NB 4.1) because it leaves the code in a incoherent state that no longer compiles a that you cant undo easily if not worse...
> But please absolutely avoid modifying half the files (this happened with VSS generics and NB 4.1) because it leaves the > code in a incoherent state that no longer compiles a that you cant undo easily if not worse... did you try it out? there should be a dialog informing yo that refactoring plans to checkout some files before the ref starts at all.
Hmm interesting. I didn't try it yet because this might corrupt my current project. I tried to refactor one method and the file became hijacked after that!? This brings me to the "working with hijacked files": I cannot undo the change (no revert or undo hijack options available) and delete the file from NB will probably delete it in the repo. My only option is to use the CC tools the undo the hijack...
> I tried to refactor one method and the file became hijacked after that!? sounds like a bug. any chance to find out how exactly was the scenario? i understand that this could be dangerous on productive data ...
Refactoring doesn't work well: - Refactoring doesn't check out the impacted files. - It doesn't work too when you try invoke, say "rename" method refactoring on a class that is not already checked out. It just does nothing. Same behavior with "preview"
you mean it doesn't work for you in general, or only if you have files which are remotely reserved?
In general
this was with a snapshotview, right?
Yes
well, i was able to reproduce some strange behavior with the state around beta. the problems should get fixed in scope of issue #130044