| Reporter |
John-Mason Shackelford (John-Mason.Shackelford)
|
|---|---|
| Created | Mar 11, 2011 9:13:35 PM |
| Updated | Dec 14, 2011 10:22:36 PM |
| Priority | Normal |
| Type | Bug |
| Fix versions | No Fix versions |
| State | Submitted |
| Assignee | Irina Chernushina (irengrig) |
| Subsystem | Version Control. Perforce |
| Affected versions | No Affected versions |
| Fixed in build | No Fixed in build |
When renaming a file in Perforce the proper way to do so is to call p4 integ to copy the old file to the new followed by p4 delete to remove the old file. This allows Perforce to track history through the rename. RubyMine 3.0 appears to handle renames by calling p4 add instead of p4 integ which means I will not be able to properly track history on the file and it also messes up the ability to do proper merges. This works correctly in the Eclipse plugin and I was surprised to find that RubyMine, which is superior to the Ruby Eclipse plug-in in many ways, doesn't properly handle refactorings from the version control side.