Labels

Ubuntu (5) Jax-RS (4) angular.js (4) java (4) linux (4) Jersey (3) classloader (3) javascript (3) Angular-UI (2) Eclipse (2) Google Chrome (2) Liferay (2) RAD 7.0 (2) SSL (2) WAS 6.1 (2) ATI Radeon 2600 (1) Apache (1) Axis (1) Birt (1) Bootstrap3 (1) CORS (1) CompizConfig (1) Finder (1) Generator (1) Google Docs (1) Grunt.js (1) JAX-RPC (1) Junit (1) Liferay javascript (1) MySQL (1) Power Mock (1) Python (1) Rest client (1) Service Builder (1) Subclipse (1) Unity (1) Virtual Host (1) Web Services (1) WebGL (1) WebStorm (1) bash (1) drivers (1) ext plugin (1) jvm (1) node.js (1) openVZ (1) play framework (1) validation (1) yeoman (1) yo (1)
Showing posts with label Subclipse. Show all posts
Showing posts with label Subclipse. Show all posts

January 15, 2013

Fix Subclipse setup in RAD 7.0

My RAD subclipse setup was broken. I had to work on that computer, wokrpsace was already set up when I started to use it and that was fine for me. But now, time to commit... and I get a nice error popup saying that "This client is too old to work with working copy" (error message is pretty clear).

So what to do ? well,  for sure not what I did : install the latest subclipse version (1.8.x) without checking first the SVN server version. In fact, i should have install the 1.6.x subclipse plugin.

I then tried to install the 1.6.x version via the update site, but I guess that after that my RAD setup didn't like to have both subclipse version installed...

RAD 7.0.x doesn't make it easy to uninstall plugins, so here's what I did to fix it and have 1.6 subclipse plugin working :
  • Shut down RAD
  • Move all thee org.tigris.something jars and folders out of the plugins eclipse directory. That made both 1.6.x and 1.8.x versions not to work.
  • Restart RAD
  • Use the following item menu to check what's really missing : Help / Software updates / Manage configuration



  • From there I was able to 
    • Disable 1.8.x version (still don't know how to remove it entirely though)
    • Diagnose what jars were missing to make the 1.6.x work fine : before I put the right jars back to the plugin directory, the corresponding items were flagged with a red cross in the above snapshot (just like a java compilation problem). Using the Display properties link helped me to retrieve the "good" jars and make the red cross disappear.
What made this a bit painful was that I had to restart RAD workspace after each item fix : fix JNA library by replacing the jar > restart RAD > check that red cross disappeared > see cwhat's nex jar missing > fix xxx library ... > ...
Without restarting in between each fix, my workspace would crash.