You need to log in before you can comment on or make changes to this bug.
Rename of a Project under Mercurial control, with option selected to rename directory also, will result in renamed Project no longer being under Mercurial control. The original projects .hg repository directory is lost in this rename scenario. 1, Create a new Java project (e.g. JavaAplication1) and initialize it as Mercurial project and Commit 2, Refactor - rename the whole project, select option to rename Directory as well What we see is the renamed project appears, but it is no longer under Mercurial control. In the process of doing the copy and rename it appears that the .hg folder is deleted and not copied over to the renamed directory.
This is a known issue and effects Subversion and CVS. It is to do with th implementation of rename and out of the mercurial plugin's control.
This is a general problem of all VCS supported by the IDE. Changing to FEATURE.
*** Issue 142616 has been marked as a duplicate of this issue. ***
In issue 142616, the problem occurred when renaming a non-version-controlled directory with version-controlled subdirectories. So it applies to a broader set of circumstances than just renaming the Project directory.
