[DougMH]

… trying to get new 7.X versions of MyEclipse to work I just can’t stand it anymore.

It was working Friday, now when I boot up Monday.

An internal error occurred during: “Initializing Java Tooling”.
assertion failed: Path for IClasspathEntry must be absolute: MYECLIPSE_LIB_HOME/EE_5/javaee.jar

I’m asking you to please work this error ASAP. I must get back to work.

[DougMH]

Here’s my latest 7.1.1 installation summary. This IClasspathEntry thing goes clear back to MyEclipse 6.X. It seems someone should have come up with a solution by now.

*** Date:
Monday, March 30, 2009 7:44:25 AM EDT

** System properties:
OS=WindowsXP
OS version=5.1.0
Java version=1.5.0_11

*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 7.1.1
Build id: 7.1.1-20090310

*** Eclipse details:
MyEclipse Enterprise Workbench

Version: 7.1.1
Build id: 7.1.1-20090310

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\Program Files\Genuitec\MyEclipse 7.1\myeclipse.exe
-name
Myeclipse
–launcher.library
C:\Program Files\Genuitec\MyEclipse 7.1\../Common\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731\eclipse_1115.dll
-startup
C:\Program Files\Genuitec\MyEclipse 7.1\../Common\plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20080819.jar
-clean
-configuration
configuration
-vm
C:\Program Files\Genuitec\Common\binary\com.sun.java.jre.win32.x86_1.5.0.011\bin\client\jvm.dll

[support-joy]

Hi,

Sorry to hear that you are facing this issue. Can you click on Window > Preferences > MyEclipse Enterprise Workbench > Project Capabilities and hit [Restore Defaults] button on each library screen. Let me know if this helps.

[DougMH]

I did as you asked. After I was done, I got sever dialogs telling my settings were wrong. I hit restore default on all dialogs where it had a restore default button, then when I was done, I got a series of dialogs, I think 5 in all, that had exactly the same message I initially reported:

An internal error occurred during: “Initializing Java Tooling”.
assertion failed: Path for IClasspathEntry must be absolute: MYECLIPSE_LIB_HOME/EE_5/javaee.jar

[DougMH]

Just FYI, I did a search of *.* in my workplace and can’t find IClasspathEntry in ANY file.

[support-joy]

An internal error occurred during: “Initializing Java Tooling”.
assertion failed: Path for IClasspathEntry must be absolute: MYECLIPSE_LIB_HOME/EE_5/javaee.jar

Looks like the reference to a file may be corrupted or a file/resource is not well formed. Can you drill down to the jar file above – *MYECLIPSE_LIB_HOME/EE_5/javaee.jar*. Try to see, where do you have the reference to javaee.jar and remove the reference. Then perform a clean. Open the MyEclipse with -clean. Or from MyEclipse menu go to Project > Clean and perform a – *Clean all Projects*

[DougMH]

Having reinstalled 7.1.1 All-in-on for the upteenth time and importing my projects, I worked all day without insicent. I closed MyEclipse at the end of the day.

This morning, HAVING CHANGED NOTHING, same error:

An internal error occurred during: “Initializing Java Tooling”.
assertion failed: Path for IClasspathEntry must be absolute: MYECLIPSE_LIB_HOME/EE_5/javaee.jar

Fortunately, I was still able to access and work on my project this time.

I’ve searched *.* for IClasspathEntry and MYECLIPSE_LIB_HOME and javaee.jar without result

-clean is in myeclipse.ini (see below)

Doesn’t the program always start with a clean?

-startup
../Common\plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20080819.jar
–launcher.library
../Common\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731
-clean
-configuration
configuration
-vm
C:\Program Files\Genuitec\Common\binary\com.sun.java.jre.win32.x86_1.5.0.011\bin\client\jvm.dll
-vmargs
-Xmx512M
-XX:MaxPermSize=192M

[support-joy]

Can you check if you have MYECLIPSE_LIB_HOME set in your environment variable? There is definitely a broken reference. Sometimes windows search doesn’t return hidden files, it depends on the options you have set for search. Can you track down what this is referring to -> MYECLIPSE_LIB_HOME ?

[support-joy]

douglasmhurst,

I want you to do one more thing. Can you go to your MyEclipse workspace. This will list you all the Projects and .metadata. Each project contains a project file and a classpath file. Can you check, if you can narrow down *MYECLIPSE_LIB_HOME/EE_5/javaee.jar* here?

Thanks for your help.

[DougMH]

@support-joy wrote:

douglasmhurst,

I want you to do one more thing. Can you go to your MyEclipse workspace. This will list you all the Projects and .metadata. Each project contains a project file and a classpath file. Can you check, if you can narrow down *MYECLIPSE_LIB_HOME/EE_5/javaee.jar* here?

Thanks for your help.

1) Regarding the last two posts, I was using MyEclipse Search, not Windows search. I was using *.* case-insensitive.

2) I have no MYECLIPSE_LIB_HOME windows environment variable. I can’t imagine that I should have.

3) I see the following in .project for all my projects that use j2ee

<buildCommand>
<name>com.genuitec.eclipse.j2eedt.core.J2EEProjectValidator</name>
<arguments>
</arguments>
</buildCommand>

4) I see the following in .classpath for all my project that use j2ee

<classpathentry kind=”con” path=”melibrary.com.genuitec.eclipse.j2eedt.core.MYECLIPSE_JAVAEE_5_CONTAINER”/>
<classpathentry kind=”con” path=”melibrary.com.genuitec.eclipse.springframework.MYECLIPSE_SPRING25_J2EE”/>

[Brian Fernandes]

Douglas,

MYECLIPSE_LIB_HOME is an internal MyEclipse variable configured based on the locations of a plugin in your installation. The “assertion failed: Path for IClasspathEntry must be absolute:” error you see had been around for some time, but was fixed for MyEclipse 7.0. Unfortunately, it can still be caused in rare cases by a corrupted workspace state. I have a few questions and suggestions:

1) Can you clear your error log and restart MyEclipse. When the startup is complete can you paste the resulting log file here – there should be other errors logged which should shed more light on the problem.
2) Is this a large workspace? i.e. many projects with a large number of libraries on their build paths? Have you been using this workspace for awhile or is this a new workspace recently created?
3) For the near term, to fix this problem, I would suggest simply switching to another workspace (File > Switch Workspace) and importing all your projects into it.
3b) Odd as it may seem the problem may correct itself if you remove the -clean switch from your myeclipse.ini and restart MyEclipse. If it does not, please put it back and switch your workspace as described above.

Sorry for the inconvenience caused, I hope this helps.

[DougMH]

1) I’m not sure which error log? directory?
2) It’s a small workspace because I’ve reinstalled MyEclipse 7.1.1 so many times, I’ve only imported my most important projects
3) See 3b) below
3b0 I did 3b from your last thread and it seemed to worked! Can I now put the -clean back in or will it cause problems again?

[Author]

Posts