Ok, I’ve now twice wasted time on trying to figure this out and this time I’m writing it down, so I don’t do it a third time

I recently added an eclipse project to SVN (it’s already in perforce, my usual SC of choice) and after that my JAR export would fail with a bunch of “Resource is out of sync” errors. Since all the resources were .svn related, I blamed SVN and chased this down the wrong path for a bit.

Here’s the simple solution: If you see a jar export fail because of “resource is out of sync”, try doing a Refresh on the project before anything else. That should solve it.

Being an eclipse newbie, setting up third party JARs was a bit painful to figure out. Well, not painful as such, just painful once i tried to move the project across platforms.

See, I was using the External JARs… option in the Build Path dialog. But that set up absolute paths, which is a bad idea even if you stay on the same platform. Going across platforms C:\.. just wasn’t an option. So i tried editing the .classpath by hand. That just created tied the path to the root. Finally I figure out that if i added a lib directory to the project, the JARs I put inside of it, were now browsable by the Add JARs option. Now everything build happily across Mac and Windows. Joy.