Re: Multi User Development one project HOW ??
Re: Multi User Development one project HOW ??
- Subject: Re: Multi User Development one project HOW ??
- From: MacFirst <email@hidden>
- Date: Mon, 20 Dec 2004 10:45:23 -0800
on 12/20/04 10:35 AM, David LeBer <email@hidden> went on and on
saying, in part:
> On Dec 20, 2004, at 1:11 PM, Clint Fleetwood wrote:
>> My business partner and I have problem. We need to both work off of
>> the information from his computer to keep the project consistent. When
>> ever I connect (I log on with his username and password remotely) to
>> his computer (Power MAC G5) with my computer (iMAC G5) and open the
>> project we keep on having to telling it not to revert to the info from
>> his hard-disk. We also have some problems with the project not saving
>> components in the project when we are both running the project. My
>> question is this: Is there a good way to set up our Machines so that
>> we can work on the same project (on his computer) from both of our
>> computers, we need the project to remain on his computer however.
>> help please.
>> -clint
> You don't share the code, you both keep separate copies and use a
> version control system to keep them in sync.
>
> CVS or Subversion are two that come to mind. CVS is the old dog,
> built-in support in XCode and Eclipse but a little crotchety.
> Subversion is the new kid on the block and has a number of proponents,
> but I've never used it so I speak from *no* experience. :-)
>
> ;david
I've used both -- CVS is familiar and has lots of support (including nice
GUI tools! :), SVN is nice, in that it's the "we tried to make it like CVS,
but fix all the stupid problems" open source version.
CVS will make it easier to talk to the old timers; SVN is probably the
"better" product.
The general flow of things is:
* There's a CVS/SVN server where lives the code "repository".
* You get a "locked" copy of the code
* Your friend gets a locked copy of the code.
* Your friend unlocks (MRO-s) and works on fileA and fileB
* You MRO and work on fileB and fileC
* Your friend checks in fileA & fileB
* You check in fileC, get the latest copy of fileA, and notice that there
are other changes to fileB (CVS/SVN makes all of this easy for you.)
* If the changes to fileB don't overlap, CVS/SVN just merges them for you.
If you both changed the same line/section of code, it calls out the
conflict, and you adjust it by hand (probably after talking to friend.)
* You check in the new fileB (vsn 3!), later, your friend will check out
fileB & C, getting all your changes mixed in with his.
This is a gross oversimplification, but that's the gist of it.
Luck!
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden