The terrors of detecting Eclipse
I was trying to install Adobe Flex Builder 2 Plug-in for Eclipse along with the Flex SDK when I encountered a problem. I was confronted with a screen in the installer that said:
Please choose an existing Eclipse folder (3.1 or greater), to be updated with the Flex Builder 2 Plug-ins.
This folder must contain the eclipse.exe file, and the standard Eclipse folder name "configuration".
I chose the directory for my Eclipse 3.3.1.1 and got this error:
Please choose an existing Eclipse folder (3.1 or greater) to be updated. This folder must contain eclipse.exe and the standard folder named "configuration"
I found other people who had the problem on the Adobe Forums.
It seems like the only solution is to install an older version of Eclipse.
This is not the first time I've had this problem with Eclipse. When I was experimenting with the Oracle BPEL Process Manager, I tried to install an Eclipse based plugin that would allow you to graphically create BPEL systems. I ran into the same exact error, and eventually had to install a second copy of an older version of Eclipse to get the plugin to install.
I'm curious about the process a developer goes through to detect Eclipse. Based on the appearance of both of these installation programs I've seen, I assume they are both Java based. This makes me think they are using the same code base for their respective installers, and the person at fault is not Oracle or Adobe, but the person who wrote the Java installer, or the Eclipse foundation.