Okay, I think I got it.
Its freakish, but I got it.
Commit sends your version to the server.
Updating sends the server’s version to your local site
synchronizing tries to to both at the same time.
The thing you need to know about Eclipse, that might save you headaches, is that, when synchronizing the left window is the local version and the right window is the remote version. NOT THE OTHER WAY AROUND.
I think the windows are actually labeled when you’re doing “every day” sycnchronizing… but not when you’re doing the “I’m mapping this project to a CVS database for a first time” synchronizing. (My local version is not up to date for every file. Some files are more up to date than the remote database.)
A little labelling might’ve helped me to not fuck up my remote database.
Well, I caught on after having messed up only two files… (that’s before I figured how I could’ve messed up a whole packages in one signe shot – or the whole project). So I said unto myself: “no problem. I’ll just roll back to my previous version for these files. No biggie, right? right? RIGHT??
Well, I’ve still to figure ou the rollback thing. I figured I can tag a file to an older version (and can no longer update it). Ended up figuring out how to get rid of the friggin flag.
What I ended up doing is getting version 1.1 of the file and committing the changes. So now my files are up to 1.3. But 1.2 is useless and I would’ve wanted to thrash it.
If you’re into Eclipse and CVS, help, enlightment and tips & tricks are welcome!!