| Synchronization Across Different Computers [message #259739] |
Tue, 01 July 2008 18:20  |
Eclipse User |
|
|
|
Originally posted by: kinnetica.gmail.com
Is there any way to have Eclipse synchronize and download changes that
have been made on another computer. This kind of tool would be very
convenient since I usually work on the same project at home and at work
and would prefer not to send myself the updated files of the same project
each time.
Thanks,
Michael
|
|
|
|
| Re: Synchronization Across Different Computers [message #259744 is a reply to message #259742] |
Tue, 01 July 2008 22:48  |
| Eclipse User |
|
|
|
Eric Rizzo wrote:
> Michael Levin wrote:
>> Is there any way to have Eclipse synchronize and download changes that
>> have been made on another computer. This kind of tool would be very
>> convenient since I usually work on the same project at home and at
>> work and would prefer not to send myself the updated files of the same
>> project each time.
>
> Yeah, its called CVS (or Subversion or ClearCase or
> <insert-favorite-SCM-system-here>).
> Seriously, it is pretty easy to set up a CVS server these days and it
> will eventually save your butt when you accidentally do something silly
> like delete an entire source tree.
>
> In lieu of that, have you tried File > Export to move projects around?
>
I'll second this. I just got started about a month ago using Subversion
(and the Subclipse plug-in for Eclipse), because I found myself
compiling two versions of the same code (different target machines,
different versions of a third-party library). Not only does it (a) let
me access code from one either machine from a central repository and (b)
implicitly provide a backup copy, but it also makes going off on snark
hunts easier. If I want to try something that's going to involve a
bunch of changes, just to see if it works, I create a new branch. Then
I can always return to reality just by switching back to a different
branch. Plus it documents things that I tried and backed off on. It
indirectly helps with debugging too (and I've sadly been doing a lot of
that the past few weeks). I can add all sorts of print statements and
debugging trash, saving the file to disk each time but not committing it
to the repository, and when I'm done I just tell Eclipse to revert to
the last committed version and it cleans up all the temporary stuff.
There's a bit of a learning curve, but it's not too bad, and the
learning has already paid for itself.
/Paul
|
|
|
Powered by
FUDForum. Page generated in 0.08716 seconds
Home