Hi! I’ve been reading your web site for some time now and finally got the courage to go ahead and give you a shout out from Humble Tx! Just required to tell you keep up the good work!…

Alternatively, I’m using Git locally (I’m new to Git) with Egit in Eclipse, so I might try pushing my code to GitHub as a backup.

The other issue is the network traffic involved. The dropbox daemon sends a copy of every changed file to the server (where you’re working) and pulls it down from the server (on all other systems where you have dropbox running) so your network usage can really add up. That’s a good use of network resources if you’re creating new content, e.g., editing source files, but your class files can be regenerated at any time from your source files – there’s no real gain in distributing them to other dropbox instances. That’s the other concern I had when putting all of my class files in a different directory.

I was planning to put the Eclipse project folder in Dropbox, as per your Second Attempt. It would seem a good approach. My Ubuntu set up is a single main partition, including /home, with plenty of space.

In your description of the problem with your Second Attempt, you mention the changes log maintained by Dropbox. Is this on their website?

I do wonder whether it’s wise to use something like Dropbox to sync a dev environment that is frequently generating new versions of build files. There would be a lot of updates. My alternative plan is to periodically (maybe manually) create a ZIP archive of my Eclipse project and copy this to Dropbox, keeping the actual project folder outside of Dropbox.

I’d be interested in your thoughts on this and to hear how you are getting on with your own Dropbox Eclipse set up.

–Thomas.