Howdy. I updated my J2SE today, and put it in a different directory from where the old version was. When I try build/running an app in Eclipse (3.0.1), it gives me this error: "Specified VM install not found: type Standard VM, name J2SDK 1.4.2.03".<br> <br> I've added the new SDK in Preferences>Java>Installed JREs, and the new JRE that it installs automatically in 'C:\Programs Files'. Neither make it work. I've even deleted the eclipse folder, and downloaded it over and put it back, same thing. Any help please? Thanks. :)
Yeah, when I first tried Eclipse, it took me about an hour just to get it to run. I was getting similar errors. After fooling around, I found the trick (or a trick that worked) was to launch it like so:
Actually I just found a workaround. I made a copy of the JRE tot he folder where the old one was, started Eclipse, and rechanged again all the LIbrary references to the new JRE. Then I closed it, deleted the folder with the "old JRE. After I started Eclipse, it didn't give me any problems. I guess it just likes to be "consulted first" when you're deleting a JRE from the system. Delete references to it in Eclipse, then you can uninstall it from your system. :)
This happens to me every time I try to bring in a project configured for one machine to another. And don't even try creating a windows shortcut from the real jdk to the name it's complaining about -- chyeah, right. So, instead of deleting the files ('coz some of them might take a while to configure), you can open them up (your project *launch files) and change the VM_INSTALL_NAME to the entry on your box (not the full path, mind you). I believe that this entry is a reference to something in .plugins/org.eclipse.jdt.launching/libraryInfos.xml ... but could be wrong. Maybe someday I'll pin it down further.
Worst case, delete the launch files and start over.
> Try deleting these files: > .../.metadata/.plugins/org.eclipse.debug.core/.launches/*. > launch > > --Roger trying to solve the same problem after a full day spent on it, I was getting crazy (and sad) because it seemed that nothing was working :-(((
and after all, it necessitated to delete a couple of files (simple but impossible for me to be guessed)...
> > Try deleting these files: > > > .../.metadata/.plugins/org.eclipse.debug.core/.launches/*. > > > launch > > > > --Roger > trying to solve the same problem > after a full day spent on it, I was getting crazy (and > sad) because it seemed that nothing was working :-((( > > and after all, it necessitated to delete a couple of files > (simple but impossible for me to be guessed)... > > thank you very very much
-Deleting old launch files helps -- Thanks for the tip. I reiterate. Deleting the launch files works. In the process I was able to clear out a bunch of old ant tasks. Also, you are able to toggle between virtual machines and remove some problems with base code that differs between 1.4.2_08 and 1.5_02.
-vm no help fyi, as previously posted passing the virtual machine location via -vm "<bin path>" did not seem to make a difference.
Great info! Helped me a lot. Maybe that what I realized is obvious to everyone else, but in case not:
1. The .metadata directory is at the root of the eclipse workspace.
2. Killing the launch files removes the launch entries from the run, run external, and debug menus in eclipse. Really, it looks like only the build launch files contain a jdk reference.
3. Eclipse needs to be restarted for these changes to take effect.
Unfortunately killing the launch files for Eclipse usually means you have to re-configure the project which is quite arduous if your project is significantly large. That's the point at which Eclipse makes me wince (I find this to be quite a drag).
a simple solution is to check Windows | Preferences | Java | Installed JREs to see if one of the listed VMs name matchs the missing VM name. If not, just create a new VM or rename an existing one.