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.
Suppose the directory structure of your project is as follows: - MyProject + nbproject - svn + .svn (hidden) + src + web build.xml The contents of the "svn" directory are under version control. If I rename the project (and select "Also rename Project Folder"), NetBeans performs "svn delete" operations on the entire version-controlled tree and then copies that tree (without the subversion metadata) to the new project location, leaving the "empty" tree in place of the old location. I suspect this occurs with other version control systems too, and it may happen when simply renaming any parent directory of a version-controlled directory. These operations should not touch any version-controlled files. The parent directory should simply be renamed or moved, as appropriate to the operation.
*** This issue has been marked as a duplicate of 87567 ***
isn't a duplicate
reporter comment taken from 87567: If an operation (such as move or rename) is performed on a non-version-controlled parent directory which contains version-controlled files, that operation should not trigger any version-control operations. Currently it does, and that causes problems. In this case, the operation should affect only the local file system, copying the working copy and all relevant versioning metadata from one location to another without modifying any of it. The issue which was just marked as a duplicate is about this case specifically. I don't think it's a true duplicate, but it is related to how NetBeans handles renaming and version-controlled files.
*** This issue has been marked as a duplicate of 135882 ***