I want to copy an existing solution to a new one with a different name. It’s not a ‘fork’ in the sense that I want to merge changes back in later, I want to do a ‘revision 2’ while leaving the original, working solution intact.
What’s the best way to do that ?
Nobody?
Well I can only assume then that either
(a) This is so simple that nobody is even going to dignify it with an answer or
(b) There is an embarrassing silence because it should be simple, but isn’t.
I would tag the current revision in SVN (svn:\myproject\tags\rev.1) and use the trunk to continue development on rev 2.
I vote A
You have to make an export and import it again in developer and when you do, make sure to check “clean import”. Then it will ask you to enter a new name for the solution.
I assumed it is OK that the 2 solutions will use the same datamodel/database.
Hi Alan,
You got 2 options given here and each have their own challenges.
Jos is talking about branching your code in a SVN (or other team server). This makes it ‘easy’ to work on a branched version to test things out, etc. while your main version (trunk) can develop separately.
Then later you can merge the 2 branches into trunk which is not that straightforward but doable.
Of course you also mentioned you wanted to rename the solution. That means you are renaming the Eclipse project.
The last time I did this it was a major pain for me. Perhaps I did things wrong but in the end I threw away my local copy and checked out the source again to get things working for me again.
Perhaps others have better experiences with this.
Joas is talking about doing a clean import of your solution. This will make it a unique new solution in your workspace (even the same workspace as the original). When you had your solution shared in a team server (SVN or otherwise) you will loose this link with the teamserver. It is than as if you created a whole new solution so merging code back would have to be done manually.
So depending on what you want to do exactly one or the other option will give you the least issues.
ROCLASI:
Joas is talking about doing a clean import of your solution. This will make it a unique new solution in your workspace (even the same workspace as the original). When you had your solution shared in a team server (SVN or otherwise) you will loose this link with the teamserver. It is than as if you created a whole new solution so merging code back would have to be done manually.
I suggested this, because he mentioned in the topic start that he does NOT want to merge the changes back. Of course if you use svn you have to share the solution again.
Many thanks everyone.