从 StarTeam 5 迁移到 Subversion 的策略?
我需要将一个大型项目从 StarTeam 5 迁移到 Subversion,并且我想保留(至少)5-10 个主要版本的快照。 我考虑了以下事项:
- 每个快照的手动或脚本导出/导入。 优点:简单、易于选择带有标签/日期的版本。 缺点:费时、不保存评论。
- Polarion 在 svnimporter 中提供了看似完美的工具,但它需要 StarTeam 8.0 中的 .jar 文件,而 StarTeam 5 中不存在该文件。优点:自动化、完整。 缺点:需要升级到StarTeam 8.0才能一次性使用。
- 通过某些中间存储库进行迁移(例如 StarTeam -> CVS -> Subversion)。 我还没有找到任何可以与StarTeam合作的中介。
- 仅迁移最新源。 优点:简单、快速,鼓励开发人员发明新的解决方案而不是重复历史。 缺点:鼓励开发人员发明新的解决方案而不是重复历史。 :-)
我很感激您提供的任何经验或建议。 谢谢。
I need to migrate a large project from StarTeam 5 to Subversion, and I'd like to keep snapshots of (at least) 5-10 of the major releases. I've considered the following:
- Manual or scripted export/import of each snapshot. Advantages: straightforward, easy to select labeled/dated versions. Disadvantages: time-consuming, does not preserve comments.
- Polarion offers what seems to be the perfect tool in svnimporter, but it requires a .jar file from StarTeam 8.0 that is not present in StarTeam 5. Advantages: automated, complete. Disadvantages: requires upgrade to StarTeam 8.0 for one-time use.
- Migrate via some intermediate repository (e.g. StarTeam -> CVS -> Subversion). I haven't yet found any intermediary that will cooperate with StarTeam.
- Migrate only the latest source. Advantages: simple, fast, encourages developers to invent new solutions rather than repeating history. Disadvantage: encourages developers to invent new solutions rather than repeating history. :-)
I'd appreciate any experiences or suggestions you might offer. Thank you.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(4)
您可以在评估期(30 天?)内运行 Star Team 服务器,而不需要 Borland 的额外许可 - 这将为您提供充足的时间来运行一些练习,并为您提供完整、可靠的解决方案。 非常值得付出努力。
另外,不要低估保留源历史记录的价值。
11 月 6 日更新:我参与的一个项目使用 Polarion 工具将单个 StarTeam 项目迁移到 SVN。 花了一点功夫,但最终的结果是完美的。 非常值得花时间投资。
You can run a Star Team server for an evaluation period (30 days?) without requiring additional licensing from Borland - this would give you plenty of time to run a few practice runs, and give you a complete, reliable solution. Well worth the effort.
Also, don't underestimate the value of retaining your source history.
Updated Nov 6: One project that I'm involved with has used the Polarion tool to migrate a single StarTeam project into SVN. Took a little bit of work, but the end result is flawless. Well worth the time investment.
关于StarTeam 版本的评论:是的,Polarion SVNImporter 工具确实需要starteam80.jar,是的,StarTeam SDK 2005 只有一个名为starteam70.jar 的文件。 但是我发现您可以通过将 starteam70.jar 复制到 SVNImporter lib 目录并将其重命名为 starteam80.jar 来作弊。
Regarding the comments about StarTeam versions: yes, the Polarion SVNImporter tool does need starteam80.jar, and yes, the StarTeam SDK 2005 only has a file called starteam70.jar. However I've discovered that you can cheat by copying starteam70.jar into the SVNImporter lib directory and renaming it starteam80.jar.
由于没有使用过 StarTeam,我无法谈论这一点 - 但我认为您已经提出了一些不错的选择。
Having not used StarTeam I cannot speak to that -- but I think you've laid out some nice options.
我正在努力使用 Polarion 套件将 StarTeam 8 迁移到 SVN。 我得到:
[main] DEBUG STProvider:80 - checkout ...relative/path/to/build.xml version:1.0
09:25:10,378
[main] INFO HistoryLogger:84 - 捕获异常:java.lang.UnsatisfiedLinkError: com.starbase.util.NativeFileAccess.setLastModifiedAsLong(Ljava/lang/String;J)V
并且目标文件存在,但我怀疑它无法解析相对路径。 您知道是否可以设置一些属性(除了 config.properties 文件中的属性之外)来控制这一点?
I'm struggling to migrate StarTeam 8 to SVN using the Polarion kit. I'm getting:
[main] DEBUG STProvider:80 - checkout ...relative/path/to/build.xml version:1.0
09:25:10,378
[main] INFO historyLogger:84 - EXCEPTION CAUGHT: java.lang.UnsatisfiedLinkError: com.starbase.util.NativeFileAccess.setLastModifiedAsLong(Ljava/lang/String;J)V
and the target file exists, but I suspect that it's unable to resolve the relative path. Do you know if there are properties (other than the ones in the config.properties file) that can be set to control this?