Java (jre 8 Or Above) 32-bit
Brandi Baylon
Installing Eclipse is relatively easy, but does involve a few steps and software from at least two different sources. Eclipse is a Java-based application and, as such, requires a Java Runtime Environment or Java Development Kit (JRE or JDK) in order to run.
Regardless of your operating system, you will need to install some Java virtual machine (JVM). You may either install a Java Runtime Environment (JRE), or a Java Development Kit (JDK), depending on what you want to do with Eclipse. If you intend to use Eclipse for Java development, then you should install a JDK. If you aren't planning to use Eclipse for Java development and want to save some disk space, install a JRE.
A Java 17 or newer JRE/JDK is required, LTS release are preferred to run all Eclipse 2023-06 packages based on Eclipse 4.28, with certain packages choosing to provide one by default. The Installer now also includes a JRE--consider using the Installer. Please see 5 Steps to Install Eclipse.
A Java 17 or newer JRE/JDK is required, LTS release are preferred to run all Eclipse 2023-03 packages based on Eclipse 4.27, with certain packages choosing to provide one by default. The Installer now also includes a JRE--consider using the Installer. Please see 5 Steps to Install Eclipse.
A Java 17 or newer JRE/JDK is required, LTS release are preferred to run all Eclipse 2022-12 packages based on Eclipse 4.26, with certain packages choosing to provide one by default. The Installer now also includes a JRE--consider using the Installer. Please see 5 Steps to Install Eclipse.
A Java 17 or newer JRE/JDK is required, LTS release are preferred to run all Eclipse 2022-09 packages based on Eclipse 4.25, with certain packages choosing to provide one by default. The Installer now also includes a JRE--consider using the Installer. Please see 5 Steps to Install Eclipse.
A Java 11 or newer JRE/JDK is required, LTS release are preferred to run all Eclipse 2022-06 packages based on Eclipse 4.24, with certain packages choosing to provide one by default. The Installer now also includes a JRE--consider using the Installer. Please see 5 Steps to Install Eclipse.
A Java 11 or newer JRE/JDK is required, LTS release are preferred to run all Eclipse 2022-03 packages based on Eclipse 4.23, with certain packages choosing to provide one by default. The Installer now also includes a JRE--consider using the Installer. Please see 5 Steps to Install Eclipse.
There are several package choices. Note that you can install the features from any package into any other package. If you are, for example, planning to do mostly Java development and some C/C++ development, you should download the Eclipse IDE for Java Developers and then add the C/C++ development tools via the "Help > Install New Software..." menu option.
The download will be delivered as a compressed (i.e. a ".zip", or ".tar.gz") file. Decompress this file into the directory of your choice (e.g. "c:\eclipse" on Windows) and ensure you have full Read and Execute permissions. You can optionally create a shortcut of the executable file ("eclipse.exe" on Windows, or "eclipse" on Linux).
Note that there is a known problem with the built-in decompression utility on all current versions of Windows. We recommend that you use a more robust decompression utility such as the open source 7zip when decompressing an Eclipse download. Some people report success when initially decompressing Eclipse into a root directory (e.g. c:\) and then moving it to a more appropriate home (e.g. c:\Program Files\Eclipse)
It is strongly recommended to configure Eclipse with the specific JVM that you want. See the instructions at Eclipse.iniThis is a very important step to be sure that Eclipse is using the JVM you intend and can't be influenced by any other software that might alter your system.The JVM used to launch Eclipse has no affect on whether it can compile Java sources for other Java language versions.
Use the Help > Install new software... menu option to add Kepler features to your Eclipse installation (you can, for example, use this option to add C/C++ development support). Additionally, you can tap into a vast collection of extensions provided by the Eclipse community and ecosystem via the Eclipse Marketplace Client (Help > Eclipse Marketplace). Note that not all Eclipse packages contain the Eclipse Marketplace Client.
If you've "installed" Eclipse but are having trouble getting it to run, the most likely cause is that you have not correctly specified the JVM for it to run under. You may need to edit the eclipse.ini file.
Another common mistake on Microsoft Windows is a mismatch between the "bittedness" of Eclipse and the JVM/JDK. This is the most frequent cause of an Error 13. 64-bit Eclipse requires a 64-bit JVM, and 32-bit Eclipse requires 32-bit JVM--you can not mix-and-match between 32-bit and 64-bit, so make sure the version of Eclipse you installed matches the JVM/JDK that you're using to run it (and make sure you're using eclipse.ini to specify the exact JVM used to run Eclipse, described above).
As a simple test, open a Command Prompt window, move to the directory that is pointed to by the -vm argument in your eclipse.ini, and run the intended java.exe with the -d32 switch to test if it supports 32-bit, or -d64 to test for 64-bit support. It's often simplest to download a version of Eclipse that will work with whatever Java you already have installed.
On more recent versions of the Mac, if you don't have a full JDK of an appropriately high version installed, the OS produces this bogus message. Installing any JRE will not eliminate this problem. A full JDK needs to be installed on the Mac.
Eclipse downloads are not password protected. This is a known problem with the built-in decompression utility on all current versions of Windows. We recommend that you either download the installer or use a more robust decompression utility such as the open source 7zip when decompressing an Eclipse download. Some people report success when initially decompressing Eclipse into a root directory (e.g. c:\) and then moving it to a more appropriate home (e.g. c:\Program Files\Eclipse)
I'm trying to install DocFetcher 1.1.7 on Windows 7 64Bit, but the normal installer does not find installed JRE. The installer says "No JRE found" and tries to download & install JRE from Oracle.
When I type "java -version" on command prompt it is displayed "java version "1.7.0" ". The Java version is installed as 32 and 64 bit, but it's an IBM version, not a Sun/Oracle one. Use of Oracle java is not permitted here.
Then I used the portable version and extracted ZIP file to scratch directory with full permissions for everyone. Here I can start GUI, but the index process throws "java.lang.NullPointerException" for every Powerpoint presentation (.ppt file).
I assume it is also a problem with Java.
I don't know the exact details of how DocFetcher tries to find the JRE (this is handled by third-party software), but in the folder DocFetcher\misc you can find an alternative launcher named DocFetcher.bat. Copy that file up into the DocFetcher folder and try to launch it.
You may change the JRE that the DocFetcher.bat uses by replacing the "java" keyword in the last line of the bat file with a path to the java executable, e.g. like so:
C:\path\to\jre\java -enableassertions -Xmx512m ...
As for the java.lang.NullPointerException errors, if they don't actually crash the whole program (in that case DocFetcher would say "Oops, this program just died!"), then please see the question "What can I do about all those errors during indexing?" on the DocFetcher FAQ.
Thanks for your answer.
I'm using the mobile version, because the installation program is unable to detect the installed JRE. I wanted to ask if this is a known issue that JRE is not found correct and how to solve it.
The other question to the problems with indexing PPT files I read the DocFetcher FAQ. As far as I see it is caused by third party tool. Does it mean it has nothing to do with the problem that e.g. installer is unable to find JRE?
Ah, okay, I thought you meant the DocFetcher executable couldn't find the JRE, when you were actually talking about the Windows installer. In that case, just use the portable version of DocFetcher; the Windows installer can't be fixed for now. The workaround with the DocFetcher.bat that I described above is not needed then.
Thanks for your answer.
I hope that the problem with "JRE Not Found" on Windows 7 will be resolved soon.
The more severe problem is that PPT are not indexed due to Java NullPointer exception.
For this I also hope that it will be fixed soon.
I will wait and give a chance to DocFetcher later ...
After some googling I found this link. It's about a NSIS plug-in which addresses the problem of accessing registry keys on Windows-64bits machines with a 32 bits installer. I think it's the way to go (provided that this plug-in is reliable enough)
The NSIS x64 plug-in will only address the problem of users having (like me) standard (Oracle) Java JRE in 64 bits version (no 32 JRE bits installed). In this case, because of the WoW64 abstraction system, the installer doesn't sees that the 64 bits JRE is installed, and it automatically downloads the 32 bits JRE (if the users cancel the download he gets "No JRE found"). It seems to me a good idea - I you feel like it's worth the effort - to include the NSIS x64 plug-in in the installer, given that DotFetcher runs fine (AFAIK) with Java 64 bits so there's no reason to install a 32 bits version of the JRE.
The initial problem of Michael is different ; he has both 32 bits and 64 bits version of Java so it's not a problem due to the WoW64 abstraction system (as far as I understand this stuff!). The IBM installer probably uses a different registry key from the Oracle one. Whether the installer checks HKLM\SOFTWARE\JavaSoft\Java Runtime Environment or HKLM\SOFTWARE\SOFTWARE\Wow6432Node\Java Runtime Environment if will make no difference if the Java Runtime is registered, for example, under HKLM\SOFTWARE\IBM\Java.
d3342ee215