FettesPS » Java http://www.fettesps.com Fettes Programming Solutions Fri, 30 Jul 2010 19:20:40 +0000 http://wordpress.org/?v=2.9.2 en hourly 1 Fixing Eclipse’s Java Dependancy Errors http://www.fettesps.com/fixing-eclipses-java-dependancy-errors/ http://www.fettesps.com/fixing-eclipses-java-dependancy-errors/#comments Wed, 07 Oct 2009 12:48:45 +0000 FettesPS http://www.fettesps.com/?p=625 While setting up Eclipse on my development station in order to compare it to NetBeans I encountered the following error:

A Java Runtime Environment (JRE) or Java Development Kit (JDK) must be available in order to run Eclipse. No Java virtual machine was found after searching the following locations:
c:\Program Files\Eclipse\jre\bin\javaw.exe 'javaw.exe' in your current path

I have Java installed, and it is working properly. It was a big pain to get working properly the first time with NetBeans so I was worried that if I tweaked it to work with Eclipse I may end up with it not working in either. I took a peek into many of the config files for Eclipse and didn’t see an option to set the path for javaw.exe, so I made use of my Google-Fu skills and found the following solution:

  • Right Click Eclipse.exe and select Create Shortcut
  • Right Click the new shortcut and select Properties
  • At the end of the target path, add the parameter -vm and then the path to your javaw.exe
    ie: “C:\Program Files\eclipse\eclipse.exe” -vm C:\Java\jdk1.6.0_13\bin
  • Hit Ok, then run Eclipse from your new shortcut

Problem solved!

]]> http://www.fettesps.com/fixing-eclipses-java-dependancy-errors/feed/ 8 Disable SVN in NetBeans http://www.fettesps.com/disable-svn-in-netbeans/ http://www.fettesps.com/disable-svn-in-netbeans/#comments Mon, 21 Sep 2009 15:23:10 +0000 FettesPS http://www.fettesps.com/?p=607 For the last couple of weeks I’ve been doing some Java development using NetBeans and every couple of days my checked out copy of the project dies on me. I was getting very frustrated because each time it happened I had to check out an older revision to a new directory, then export the corrupted one into and from there I could check it in. This was not only time consuming but a very messy solution which had the potential mess up my repository. Yet after going through all this work I would again be presented with the following error:

“This client is too old to work with the working copy “C:\path\to\repository.” You need to get a newer Subversion client, or downgrade this working copy. See http://subversion.tigris.org/faq.html#working-copy-format-change for details.”

This error was somewhat misleading, as the site it provided didn’t offer me any insight as to why it was happening. I had the newest version of TortoiseSVN and the error wasn’t happening with any of my Visual Basic or PHP projects, just the Java project. Eventually it dawned on me what was causing this. NetBeans IDE has built in support for Subversion which uses the CollabNet Subversion client. When I was working within the NetBeans IDE the CollabNet client was working behind the scenes and changing files within the .svn folder on my system. When the time came for me to check in my changes through TortoiseSVN I would get the not so helpful error message.

After a quick Google search I found the solution on the NetBeans Forums. In the NetBeans IDE go to Tools->Plugins then under the Installed tab check Subversion and hit Uninstall. The plugin will be removed and you will be prompted to restart the IDE.

]]> http://www.fettesps.com/disable-svn-in-netbeans/feed/ 3