| Eclipse will not start after changing java version in eclipse.ini [message #1801787] |
Sat, 26 January 2019 23:40  |
 thomas Strike
Messages: 6
Registered: May 2017 |
Junior Member |
|
|
I installed Eclipse neon a few years back in my computer running Ubuntu 16.04 LTS. Today, I installed the Aptana plugins for web development. When I tried to use it with Aptana Studio, some of the editors weren't working. After a lot of Googling, I found an issue with the Aptana plugin that doesn't like Java 8 so I set the vm in eclipse.ini to use the Oracle 1.7 jdk and then eclipse refused to load. I replaced 1.7 with 1.8 again and eclipse still errors out and says check the log. I look at the eclipse log and see hundreds of lines of java generated gibberish that tells me nothing. I have tried java-8-openjdk-amd64 which was running Eclipse for a couple of years and I am now pointing Eclipse at jdk1.8.0_131 which is Oracle. What should the vm line in the .ini file be pointing to or could something else have happened to be causing my problem?
[Updated on: Sun, 27 January 2019 00:00] Report message to a moderator |
|
|
|
| Re: Eclipse will not start after changing java version in eclipse.ini [message #1801817 is a reply to message #1801799] |
Sun, 27 January 2019 21:24  |
thomas Strike
Messages: 6
Registered: May 2017 |
Junior Member |
|
|
Wow, what's with the hostile attitude? I only stated a fact about why I am at a loss to troubleshoot this myself. I do not have the knowledge of the scripts that comprise Eclipse, so java errors naming the script lines that the error happened on do not mean anything to me. Again, the only thing the log contains are untrapped Java code errors. One other thing though, there is one intelligible line. It's a line that prefaces all those Java generated lines and says "java.lang.NullPointerException". Java is running into a whole bunch of variables that must not have been initialized but, again, meaningless to me since I have no knowledge of these scripts.
Let me say that the vm path seems to work whether I specify Java as a Fully Qualified line to execute or just the path to the /bin directory because I tried it both ways. They both generate Java thrown error lines, at least so I have to assume because this log file is unreasonably void of any time stamps on entry lines so I could see if the last lines were new. The vm path that I presently have in my .ini file is; "/usr/lib/jvm/jdk1.8.0_131/bin".
I came here because I do need help from people that understand what goes on behind the coding curtain and could possibly offer a little help with this. Perhaps, someone who recognizes this issue and can offer possibilities. What would help me immensely is if I could look at someone's working eclipse.ini file that was installed into Ubuntu, hopefully ver. 16.04 LTS, just to make sure that I hadn't accidentally altered or removed another line in the file without knowing. I use Ubuntu on my desktop and run CentOS in my servers on line. I haven't messed with Microsoft in 20 years.
|
|
|
|
|
|
|
| Re: Eclipse will not start after changing java version in eclipse.ini [message #1801959 is a reply to message #1801881] |
Tue, 29 January 2019 23:18 |
thomas Strike
Messages: 6
Registered: May 2017 |
Junior Member |
|
|
I noticed that most of the error lines were from Aptana as well. If it weren't the fact that after I added Aptana to Eclipse, it started up just fine and seemed to be working. What wasn't working was the HTML editor and a few others. That is why I started to search for answers and tried Java v1.7. That's when Eclipse started to fail on startup. So, I think that I did something beyond installing the latest version of Aptena that is keeping it from starting. For now, I am going to try uninstalling Aptana but I don't know how I will do that since I can't get it to start up.
[Updated on: Tue, 29 January 2019 23:20] Report message to a moderator |
|
|
|
Powered by
FUDForum. Page generated in 0.06297 seconds
Search
Help
Register
Login
Home
