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.
Let's assume you have versioned project with following structure (a and b are packages, everything was already comitted): | +---a | +---b Now create new file fl.java in package a. Do not commit it, but try to move it to package b. Move class dialog appears, confirm it. Nothing happens and fl.java remains in package a. This issue is probably related to issue #112070. Another thing is exception thrown if you select package a (in files view), invoke cut, select package b and invoke paste. When you push Refactor and it is processing the Locally New file, similar exception is thrown: org.tigris.subversion.svnclientadapter.commandline.CmdLineException: svn: 'D:\tmp\work\w1187787216761\JavaApp\src\a\b\c\NewClass2.java' is not under version control at org.tigris.subversion.svnclientadapter.commandline.CommandLine.execString(CommandLine.java:195) at org.tigris.subversion.svnclientadapter.commandline.SvnCommandLine.move(SvnCommandLine.java:580) ... ----- Product Version: NetBeans IDE Dev (Build 070822) Java: 1.5.0_12; Java HotSpot(TM) Client VM 1.5.0_12-b04
Jardo, can it be related with the issue you've fixed recently (#112070)?
A necessary condition to simulate issue 112070 is to move a folder. So I guess this issue is not related to it. Btw. I can simulate this problem on my svn repository. When I select a file under svn control, copy it to clipboard, select its folder, paste the file there (new file with _1.ext is created) and then I try to rename the file. Then I get the "is not under version control" exception. The only workaround I know is to rename the file on disk using "mv".
Well In the second part of the first description I described moving the folder. I tried older build (200708070000) and refactoring of new files worked fine there so I thought it can be related to #112070 as it was fixing similar problem. If you try to copy/move folder that doesn't contain new file (no files at all or commited files), the exception is not thrown). If it contains a new folder, it works as well. So the problem occurs only when there is new file only, therefor I thought it is related. If you are sure it isn't, should I file different issue for moving/copying folder with new file?
*** Issue 112384 has been marked as a duplicate of this issue. ***
fixed in trunk Checking in FilesystemHandler.java; /cvs/subversion/main/src/org/netbeans/modules/subversion/FilesystemHandler.java,v <-- FilesystemHandler.java new revision: 1.55; previous revision: 1.54 done
Fix verified in private build. Please integrate it also into "release60-beta1" branch. Thanks.
Semantics of the fix looks OK to me.
fixed in release60-beta1 Checking in FilesystemHandler.java; /cvs/subversion/main/src/org/netbeans/modules/subversion/FilesystemHandler.java,v <-- FilesystemHandler.java new revision: 1.54.2.1; previous revision: 1.54
Verified.
*** Issue 115142 has been marked as a duplicate of this issue. ***
*** Issue 119718 has been marked as a duplicate of this issue. ***