![]() You only CAN'T mix both, if you DON'T use -vm, but let Eclipse load Java natively into its own process using jvm.dll and such. In that case you DON'T need to have the same architecture for Eclipse and Java, but can happily mix both 32 Bit and 64 Bit. The -vm option is there to run a specific version of java and the point of it is, that the configured process is started and runs all the Java code on its own, that's why you configure up to java.exe. ![]() In my opinion the most answers here regarding different architectures of Eclipse and Java are simply wrong and this can be easily checked using e.g. And eclipse 64b will start correctly without the entry in eclipse.ini. After that the java updates do no more link to a 32b version. If you have a 64b eclipse installation and encounter the described error: just re-install the newest 64b JDK. ![]() Whatever java installer you have executed last (the *.exe) leads windows to remember that java flavour (32b or 64b), with the result that after an update the links in C:\ProgramData\Oracle\Java\javapath point to a java installation of the remembered flavour. Oracle replaces with Java8 the old technique having the symlinks in system32 (64bit) resp. It contains three symbolic links to the newest java 8 JRE installation in (x86) program folder -> hence to a 32 bit java JRE. Looking closer to the background I detected following: the chrome java updater (notabene started from an Oracle site) added C:\ProgramData\Oracle\Java\javapath in front of the env var PATH. This happened after I have installed a "chrome java updater" (Chrome browser moaned: 'your java is outdated, you have to update.').īefore this "chrome java update" my eclipse (luna jee 圆4) started without error. Mine was suddenly C:\ProgramData\Oracle\Java\javapath\javaw.exe. There you can see which java runtime in fact is started. Look at the second line of the message box. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |