问题描述
我想使用IntelliJ IDEA在SVN中继和一个或几个功能分支之间轻松切换，最好能同时处理多个分支。我有一些本地配置，如集成测试的数据库设置和启用的调试日志，我想继续使用而不是提交SVN。
I'd like to easily switch between SVN trunk and one or a few feature branches using IntelliJ IDEA, preferably being able to work on multiple branches concurrently. I have some "local" configuration like database settings for integration tests and debug-logging enabled that I'd like to keep using and not commit to SVN.
什么是各种选择的利弊，是否有一种轻松击败其他方式的方式？以下是我可以想到的一些可能的方法吗？：
What are the pros and cons of the various options, is there one way which easily beats the others? Here are some possible approaches I can think of, any more?:
-
使用SVN - 更新目录换出另一个当前分支。
不允许同时处理多个分支。
Using the "SVN - Update Directory" to swap out the current branch for another.
Won't allow working on multiple branches concurrently.
在单个项目中为每个分支创建一个模块。$
似乎导致点击堆栈跟踪/类名转到错误的模块时出现问题，很容易意外地偶然搜索模块等等？
Creating a module per branch in a single project.
Seems to cause issues with clicking on stacktraces/class names going to the wrong module, easily accidentally search across modules by accident and such?
为每个分支创建一个单独的IntelliJ项目。
每个项目的单独设置更加冗余，更多工作可以使项目之间的所有内容保持同步。减少意外使用错误分支的风险。
Creating a separate IntelliJ project per branch.
More redundant with separate settings per project, more work to keep everything in sync between the projects. Less risk of accidentally working with the wrong branch.
推荐答案
我有最佳体验
优点
- 分支机构之间快速切换。
- 您可以打开更多分支在同一时间。
缺点
- 你必须为每个分支设置构思项目。
- 仅适用于有限数量的分支。
我有一个用于主干版本的项目和用于当前生产版本的其他项目。
如果你有更多的分支然后两个，我认为第一个选择更好。
I have one project for trunk version and other project for current production version.When you have more branches then two, first option is better idea I think.
这篇关于IntelliJ IDEA中多个SVN分支的工作流程的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！