我在工作中使用 ClearCase 和 UCM 很不幸。我们试图找到一种方法，让用户在使用时获得更流畅的体验。主要问题之一是所有文件在签出之前都是只读的。这会干扰 IDE 的使用及其重构功能。无保留的签出变化不大，因为它仍然需要显式执行签出。可以以某种方式模拟编辑合并方法吗？例如，ClearCase 能否以某种方式自动对文件修改进行无保留签出，而不对其强加只读模式？
I have a bad fortune of using ClearCase with UCM at work. We try to find a way to get user experience smoother while using it. One of the main problems is that all files are read-only until checked out. This interferes with using IDEs and their refactoring capabilities. Unreserved checkout changes little as it still requires perform check out explicitly. Can Edit-Merge approach be somehow emulated? For example, can ClearCase somehow make unreserved checkout on file modification automatically and not impose read only mode on them?
发布评论
评论（1）
我们处理以下交互的方式：
是使用带有良好 ClearCase 插件的 IDE：
保留文件历史记录的唯一方法是通过像 Eclipse 这样的 IDE 进行重构而不先检出文件：ClearCase 插件 会将文件从旧名称“
cleartool move”移动到新名称，并检出/检入它们，保留它们的历史记录。另一种手动方式不太理想：
您可以在快照视图中隔离该操作，在快照视图中，仅为了此次重构，我们清除了所有文件中的只读位（因此它们都处于“劫持”状态）。
重构完成后，我们使用结果作为源导入到动态视图中。
clearfimport -mirror< /代码>。您可以使用动态视图作为目标，但最终结果是新文件，没有指向其以前文件名的链接。
主要思想是：您不会每 5 分钟甚至每天重构一次代码，因此，使用正确的工具，您可以采用一种可接受的方式来缓解 ClearCase 以文件为中心的性质。
The way we approach the interaction between:
is to use an IDE with a good ClearCase plugin:
The only way to preserve the history for files is doing the refactoring through an IDE like Eclipse without checkouting the files first: The ClearCase plugin will '
cleartool move' the files from their old name to their new names and checkout/checkin them, preserving their history.The other manual way is less ideal:
You isolate that operation in a snapshot view in which, just for this refactoring, we clear up the read-only bit from all the files (so they are all in "hijacked" state).
Once the refactoring is done, we use the result as a source to import in a dynamic view.
clearfimport -mirror.You can use a dynamic view as the destination, but the end result is new files with no link to their former filename.
The main idea being: you don't refactor your code every 5 minutes or even every day, so , with the right tool, you could have an acceptable way of mitigating the file-centric nature of ClearCase.