We are developing an application and we have a 2 teams (say X and Y) that are at different places.
Both these teams have 5 member each.
Both Teams do not work at the same time, if X team works for 9 hrs at Place A, Y team works at Place B for next 9 hrs.
Currently we are using a Visual SVN server on one of our local machine at Place A and all the team members of X team use it to sync their workspace using the Eclipse Plugin for SVN. This works fine. At the end of the day, we send the war file to Team Y at Place B. They again have the same setup and the same process.
This is becoming a trouble for us to keep the application in sync.
One of my frnd told me to use online SVN. I tried one at unfuddle.com. But I have few problems with it:
Ours is a big applicationa nd we dont have a very fast internet connection. We are looking for a solution such that all the team members of a particular place use the Local Visual SVN server to commit, update the workspace and then at the end of day, someone at Place A sync this workspace with the online workspace. Now one person at Place B can get latest code from online workspace and then the team members at location B can use it at their local server.
The problem i m facing is that I dont know how to compare a workspace with a different repository in eclipse.
David Newton wrote:That strikes me as being very error-prone. Are you sure you can't just use the same repository?
HiDavid, As I have told we have a slow internet connection. And as the update/commits are frequent in the reposittory, SO it won't be possible for our developers to do it efficientely with the online SVN. Thats why we are maintaining a local SVN.
But to keep the development work in sync with the other team we need an online SVN as well,
I am not sure if there is a solution for what I have asked.....but is there a better way to do this???
Ernest Friedman-Hill wrote:You could use a different version control system, one that doesn't use a central server in the same way; Git comes to mind.
Quite so. In fact, I think that Git was specifically designed for this sort of stuff, even including slow data links. If I haven't got my wires crossed, Git supports the ability to have local Subversion repositories that run disconnected but can be synced-up through a Git repository. Which is a really neat feature if you're developing while on the road.
Some people, when well-known sources tell them that fire will burn them, don't put their hands in the fire.
Some people, being skeptical, will put their hands in the fire, get burned, and learn not to put their hands in the fire.
And some people, believing that they know better than well-known sources, will claim it's a lie, put their hands in the fire, and continue to scream it's a lie even as their hands burn down to charred stumps.
Dinner will be steamed monkey heads with a side of tiny ads.