Eclipse on win64 - java

Is anyone successfully using the latest 64-bit Ganymede release of Eclipse on Windows XP or Vista 64-bit?
Currently I run the normal Eclipse 3.4 distribution on a 32bit JDK and launch & compile my apps with a 64bit JDK. Our previous experience has been that the 64bit Eclipse distro is unstable for us, so I'm curious if anyone is using it successfully.
We are using JDK 1.6.0_05.

I'm using Eclipse with a 64bit VM. However I have to use Java 1.5, because with Java 1.6, even 1.6.0_10ea, Eclipse crashed when changing the .classpath-file. On Linux I had the same problems and could only get the 64bit Eclipse to work with 64bit Java 1.5.
The problem seems to be with the just in time compilation, since with vmparam -Xint eclipse works -- but this is not a sollution, because it's slow then.
Edit:
With 1.6.0_11 it seems to work.
1.6_10 final might work as well as mentioned in the comment, but I've not tested that.

I've been successfully using it on Vista x64 for some light Java work. Nothing too involved and no extra plugins, but basic Java coding has been working without any issues. I'm using the 3.4M7 build but it looks like the 3.4 stable build supports Vista x64 now.

Related

Installing eclipse 2020-03, jdk 1.8, spring3 on macbook m1

I'm relatively new to mac os, java, eclipse,, simply everything, and all the changes that are being made due to the revolutionary apple silicon is driving me crazy.
My co-workers and I are working on a java project based on Eclipse 2020-03, jdk 1.8, spring 3. and I'm having trouble installing the environment on my Macbook M1.
First, I've tried installing the open jdk1.8 and have managed to set the PATH in .zshrc
Then I installed Eclipse 2020-03 and opened it using rosetta when it immediately crashed on me. It wouldn't even ask what workspace to open.
So I tried installing the new Eclipse 2022-06 (arm) and set jdk to 1.8. Eclipse worked fine until I tried making a new Spring MVC project when it gave me java.lang.exceptionininitializererror. I've searched for solutions to this error and only found 'upgrade your jdk' suggestions.
I decided to lower Eclipse version to 2021-12 (arm, because its the first arm supported), and install jdk11 + set Path in .zshrc (commented out jdk1.8 path). I still get java.lang.exceptionininitializererror when I try to create new spring legacy project.
tried:
Option 1. Eclipse 2020-03 (macOS x86_64) + jdk1.8 -> eclipse wont open
Option 2. Eclipse 2022-06 (AArch64) + jdk1.8 -> java.lang.exceptionininitializererror when creating spring project
Option 3. Eclipse 2021-12 (AArch64) + jdk11 -> java.lang.exceptionininitializererror when creating spring project
with option 3 above, I could open spring-mvc-project set in a different PC and worked fine. but I still want to have my problem solved.
I've thought over and came up with three ways to get these problems sorted:
Have exactly same Eclipse, jdk, spring version with my co-workers (option 1), try fixing start-eclipse problems.
-> slow since im using rosetta but i wont have compatibility problems with my co-workers
use most recent Eclipse, jdk, spring3
-> fast and have less problems but I assume I'll have tons of compatibility problems
use relatively old but apple silicon-supported Eclipse(Option 3), jdk 11
-> fast, have some compatibility problems (if I solve 'java.lang.exceptionininitializererror' problem)
My questions are:
Of the three ways listed above, which would you suggest me try?
How can I solve the problem I face when trying that particular way?
Additionl:
I couldn't find any related error on terminal, but I found this on my error log
Additions2:
I decided to install the relatively new Eclipse(2022-03), using jdk11. so far its working fine, without any compatibility issues
Unfortunately, it seems that Eclipse Adoptium / Temurin pointed to by rzwitserloot's answer either never had a JDK8 for MacOS aarch64, or has removed it. They have JDK11 and higher, but that's not what this question is about.
Eventually, I found that Azul offers a version of OpenJDK 8 compiled for MacOS ARM64 (Apple Silicon):
https://www.azul.com/downloads/?version=java-8-lts&os=macos&architecture=arm-64-bit&package=jdk
I have installed it and it seems to work fine.
java -version
openjdk version "1.8.0_345"
OpenJDK Runtime Environment (Zulu 8.64.0.19-CA-macos-aarch64) (build 1.8.0_345-b01)
OpenJDK 64-Bit Server VM (Zulu 8.64.0.19-CA-macos-aarch64) (build 25.345-b01, mixed mode)
You can get ARM mac versions of all JDKs including JDK8 from Adoptium.
Eclipse is highly backwards compatible. There is no sensible reason to use anything but the most recent stable release.
Eclipse itself runs on a JVM. There is no need for this JVM to be what your project standardized on, because any project in eclipse can be configured to run on whatever JVM you want. Thus, if it sounds like you need a newer JVM version to run eclipse on, just do that. It doesn't matter if your project won't run on that.
More generally getting an ExceptionInInitializerError is a wrapper exception. The real cause is inside it. Inspect the traces somewhat more rigorously; start eclipse from the command line (open a terminal, then run /path/to/Eclipse.app/Contents/MacOS/eclipse - now you can see the terminal output, that might help. "ExceptionInInitializerError" says almost nothing and has a billion causes. You want the exception that caused that, that'll be much more specific. It's somewhat unlikely to be related to running on an M1; very little stuff in the java ecosystem cares one iota about what chips you run it on.
More generally if rosetta is involved you're doing it wrong, there is no need for this. Everything relevant (which is really just the JVM, everything else runs on top of that) is available native.

Codename one missing from NetBeans plugins on Ubuntu

I am on Ubuntu 16.04 with NetBeans 8.1 - fresh install provided by Ubuntu SW center + OpenJDK - default with Ubuntu.
When I follow the video manual on codename one web site: https://www.codenameone.com/download.html
I do not get option to install codename one plugin.
To be precise, there is not a single available plugin listed.
In Windows 7 this works fine however.
I don't even know, who should I attribute this problem to:
Ubuntu 16.04 ? - which sucks and behaves weird compared to earlier Ubuntu versions (now for instance does not close the open and frozen NetBeans - had to kill -9 it)
Net Beans 8.1 ? which runs just fine with Win7
codename one ? Which I rather doubt :)
or even me ? :)
Please give me any hints, if anyone ran into similar troubles, how do I fix it ?
We need to the official Java 8 JDK for install since we need access to Java FX for things such as web browser/media support. If OpenJDK will ever work with Java FX properly then it should work fine with Codename One.
Here is the solution:
Part of the story is, that you should use original JDK from Oracle, not the pre-installed OpenJDK. Similarly, Android Studio will complain about incompatible JDK.
But secondly ! Using the NetBeans installation provided by Ubuntu SW center results in incomplete, or not updatable version. Simply you get no available plugins listed. Only those pre-installed. Moreover, this IDE freezes much too often. What the heck !?
Instead download and install NetBeans from their site:
I went for the full version.
For this and many other reasons I think I am done with Ubuntu 16.04
Every day it convinces me it does not YET deserve to occupy my disk space. I will probably step back to 14.04 LTS, until 16.04 LTS it reaches some mature state.

OSX Yosemite - JVM Shared library does not contain the JNI_CreateJavaVM symbol

Downloaded OS X Yosemite Beta 3 and I'm trying to run some eclipse based IDE's, namely Titanium Studio and Aptana Studio.
Running into this error message when I try to start the apps. Didn't work on boot, so I downloaded JDK 1.8.0_40, still no dice. It's looking in the proper location, the file exists and it's using the correct java version. Not sure what the issue is, any help would be appreciated.
Download the newest version of Java for OS X 2014-001 from Apple. http://support.apple.com/kb/DL1572?viewlocale=en_US&locale=en_US
I encountered the same error this morning and this was a quick and easy fix.
I got this problem when I try to lunch AptanaStudio 3.1 on OSX yosemite.
I google this problem for quite a lot and found that JDK1.8(64-bit) version just does not support the Aptana Studio(3.1), maybe also not working on some other IDE which based on the same skeleton of Eclipse.
The only solution I can came out is to install an older version of JDK, and I found that the link #ChancePance provide just worked for me.
Why I am answering this question is just to specify that it's OK to install this version of JDK(which is version 1.6.0_65, 64-bit when I download the package) alongside with the J2SE 1.8(provided by Oracle). So you don't have to worry about there is any conflicts while installing two version of JDK.
I need the JDK1.8 for some of the new features of the latest version of Oracle's J2SE. And I need Aptana Studio at the same time. I am quite worried about there might be some conflicts.
Below is what I have done on OSX Yosemite to solve the problem of AptanaStudio3.1:
Download and install the package: JavaForOSX.
Found the file "AptanaStidio3.ini", the file by default located under the the directory here: /Applications/Aptana Studio 3/AptanaStudio3.app/Contents/MacOS
Add "-vm" argument to specify the java which will be used to lunch Aptana Studio.
-vm
/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin/java
Hope this will help you guys who got the same problem.
I ran into this problem as well. Apparently Aptana Studio is 32-bit, while the java I have installed is 64-bit.
I didn't want to revert to Java6 as the accepted answer suggested, so I solved it another way.
I downloaded a 64-bit version of Eclipse and installed the plugin version of Aptana Studio.
I was also experiencing this problem because I had a 64 bit JDK 1.7 installed (the standard Oracle version - not the Apple version indicated in the other answers) and had mistakenly downloaded a 32 bit version of Eclipse. Doh!!
I removed the 32 bit version and downloaded the 64 bit version of Eclipse and everything works great now.
Simply downloading the newest Java for OSX worked the charm. I clicked and downloaded the file from the link above -> http://support.apple.com/kb/DL1572?viewlocale=en_US&locale=en_US <
Open "/Applications/BonitaBPMCommunity-6.5.0/BonitaBPMCommunity.app/Contents/MacOS/BonitaBPMCommunity.ini"
Obtain the location of the JRE / JDK on your system by executing in a terminal:
/usr/libexec/java_home
Add 2 lines after adapting the ...jdk1.8.0... to your system as found out above
-vm
/Library/Java/JavaVirtualMachines/jdk1.8.0_31.jdk/Contents/Home/bin/java
in between the following lines:
-clearPersistedState
-vmargs

Oracle forms in web windows 7 jinitiator not working for IE9

I was using oracle forms in WEB Windows XP with IE6 it was working well with J initiator. Now I switched to Windows 7 with IE9 I installed Jinitator but, IE is crashing.
Any solution ?
There are several solutions for this.
Ditch jinitiator and switch to JRE 1.6.0_37.
Works on Windows XP and Windows 7 and Linux (REHL 5/6 AND FEDORA 17*).
Browsers tested IE7/8/9, chrome, firefox, safari.
What kind/version of application server are you using?
What kind/version of forms are you using?
*) YES You can install oracle 11.2.0.2 database, Weblogic 10.3.6 and Forms 11.1.2.0.0 on Fedora 17
You should realize why in the past you should have used jinitiator and not a jre version. So here is some background:
When webforms gave birth oracle had a lot of bugs regarding to the java runtime. In that time java was from Sun and they didn't want to solve all the issues regarding oracle webforms. So instead of pushing Sun (if Oracle even could do that at that moment) they had the idea of doing the work themselves. So Jinitiator was the product to solve all these issues.
In the meantime Sun fixed all the problems (or at least most of them in the end of version 1.5 and the beginning of version 1.6 of java runtime), so jinitiator was becoming absolute.
At this moment java development is from Oracle and not anymore from Sun so all the problems will certainly be resolved and jinitiator can disappear from this world.
So the solution to you're problem is indeed install java runtime version in windows 7.
Hope this answer will give all of you a better insight in this matter.
I only can offer you to try Netscape browser, on Windows 7 i am running Oracle Forms with Netscape and it works well.
I tried the below and it worked.
Install Jinitiator as normal, if your having problems actually getting it to install, just use the Win7 ‘compatibility mode’ to get it to stay on your machine instead of it annoyingly uninstalling itself at the end of a failed install process.
Now
Replace the jvm.dll in jinitiator directory (C:\Program Files (x86)\Oracle\JInitiator 1.3.1.13\bin\hotspot\) with this file jvm.dll.
Restart IE* and try again, Windows 7 should reduce your color scheme and your app should now work.

msvcr71.dll file missing on Win Vista when trying to run my java swing application

I've done numerous searches and I realize that I can just download this file and install it either in windows/system32 or in the application's directory. My question is, how does this dll generally get installed on Vista? I tried installing the .net framework 3.5 and it didn't get installed with that.
Background:
I'm running a java.jar wrapped as an exe using exe4j.
msvcr71.dll is the Microsoft Visual C++ Common Runtime for Visual Studio 2003. Applications developed with VS2003 will usually install this.
i tried this fix to resolve MSVCR71.dll missing error in Windows 7 X64:
http://backspacetab.com/2011/05/09/msvcr71-dll-windows-7-x64/
Its only for 64Bit users... 32bit users follow the guide here: http://i.justrealized.com/2009/how-to-fix-missing-msvcr71dll-problem-in-windows/
Thanks and enjoy !!
have you tried executing using "java -jar java.jar"? Does it produce the same result?
Since VS 2003 targeted older versions of .NET and is not a supported development environment on Vista, it's probably only going to get installed on Vista if an application's installer does so.
I don't know if the .NET 1.1 redistributable will install it on Vista, but it's worth a try in a virtual machine.
Your problem might be related to these Sun bugs -
http://bugs.sun.com/view_bug.do?bug_id=6560269
and
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6648440
Upgrading to the latest exe4j (version 4.1) solved this issue!

Categories

Resources