SVN best practises
Hello.
I have been working with IDEA and SVN for some time and i've run into some project organization issues i thought i'd ask you about. I'm often working with large projects consisting of multiple modules and several branches from those modules, also i have a project with lots of branches with few differences and constant merging of changes between branches.
So far i've created separate module in project for every branch of every code module i need to work on. It is OK but tends to be confusing and error prone at times, also it makes for very large IDEA projects forcing IDEA to consume a lot of memory and be a bit sluggish.
I've thought about making separate projects for branches but that makes working with two branches at the same time a pain (comparing, manually tracking changes etc).
So my question is, how do you work with big projects with multiple branches. Is there anything i've missed or do i just have to carry on like i've done so far?
Please sign in to leave a comment.
Hello tanel,
We use different projects for different branches. Selena has some new features
(for example, "Compare with Branch") to make this scenario work better. Also,
Subversion merge tracking (which is planned for Subversion 1.5) will make
it much easier to track changes between branches.
--
Dmitry Jemerov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"