- This topic has 1 reply, 2 voices, and was last updated 13 years ago by
.
-
Posts
-
It is a bit embarrassing to admit this, but the project on which I am working makes no use of branching in Subversion. It appears that the people who are no longer here did not fully appreciate the advantage of being able to have each developer working on a separate branch. (As you might expect, when all development is done on trunk, the results are a disaster–and it is worse than you might expect.)
I am trying to figure out how to use MyEclipse 9 to support branching. Previously, my experience has been with SCMs such as ClearCase, where you modify a configuration spec to identify which branches to include. I am trying to figure out how to do something similar using MyEclipse 9 and Subversion. So far, the results have been pretty unpleasant and not terribly functional.
Team Branch lets you make a branch from your current source, and this is pretty obvious. What is not so obvious is how, once you have created a branch, to switch back and forth between your branch and trunk. When I try to use the Team Switch command to change to a different URL (in this case, the branch created by the Team Branch command), it updates the source from that branch into the current workspace. There seem to be conflicts, because instead of creating a new workspace for this branch, it attempts to replace (not merge) the trunk’s workspace with the contents of the branch.
I have this weird feeling that somewhere there must be a document that explains the best way to do this–but I cannot find it.
claytoncramer,
I am afraid that the issue reported by you is not MyEclipse specific but related to the subversion plugin you are using with MyEclipse.
In case you switch branches, the switch replaces code and not merge code. My two-cents. I would recommend you refer the documentation appropriate for the subversion plugin and cross-post on subversion forums.
