[Aidan Hughes]

Hi,

I’m not sure if this is a bug or configuration, but it only started happening after I installed ME 7.0M2. All was fine for a while, then I started getting an error every time I click on any file in the package explorer:

An error has occurred. See log for more details.
java.lang.NoClassDefFound Error
com/genuitec/eclipse/j2eedt/core/J2EEProjectUtil

It doesn’t seem to have any real effect – I can still open files, edit, deploy etc.

I uninstalled 5.1GA and 7.0M1. The error then disappeared for a couple of days and I put it down to some sort of conflict (I know there shouldn’t be, but …).

The error has now returned.

I can’t locate the log file it is referring to.

I’m pasting my installation summary below:

*** Date:
06 October 2008 08:20:07 o’clock BST

** System properties:
OS=Windows2000
OS version=5.0.0
Java version=1.5.0_11

*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 7.0 Milestone-2
Build id: 7.0-M2-20080915

*** Eclipse details:
MyEclipse Enterprise Workbench

Version: 7.0 Milestone-2
Build id: 7.0-M2-20080915

Eclipse Project SDK

Version: 3.4.0.v20080522-7O7S-CHEp2gcoGjmFFomLz-d5M8NdvuPgDrH17jw0Mvhe
Build id: I20080617-2000

Eclipse Platform

Version: 3.4.0.v20080610-9I96EhtEm-T_5LxIsybz-3MdGZmOA3uwv7Ka_M
Build id: I20080617-2000

Eclipse Java Development Tools

Version: 3.4.0.v20080603-2000-7o7tEAXEFpPqqoXxgaBhhhq
Build id: I20080617-2000

Eclipse Graphical Editing Framework GEF

Version: 3.4.0.v20080115-677-8082A5696H274A
Build id: 200806091334

Eclipse RCP

Version: 3.4.0.v20080324a-989JERhEk-jWnd5IY8K5tjxB
Build id: I20080617-2000

Eclipse Plug-in Development Environment

Version: 3.4.0.v20080603-7T7U-E_EkMNrNKb39WcMC
Build id: I20080617-2000

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\Program Files\MyEclipse 7.0 M2\eclipse\eclipse.exe
-name
Eclipse
–launcher.library
C:\Program Files\MyEclipse 7.0 M2\eclipse\plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.0.100.v20080509-1800\eclipse_1114.dll
-startup
C:\Program Files\MyEclipse 7.0 M2\eclipse\plugins/org.eclipse.equinox.launcher_1.0.100.v20080509-1800.jar
-exitdata
898_f8
-clean
-vm
C:\Program Files\MyEclipse 7.0 M2\jre\bin\javaw.exe

Regards,

Aidan.

[Loyal Water]

hughesai,
Have you tried starting MyEclipse using the -clean command? Does that fix the issue?
https://www.genuitec.com/forums/topic/troubleshoot-using-the-clean-command-line-argument/

[Aidan Hughes]

Hi again.

No – I hadn’t tried that – I have now though but it did not help – I’m still having problems.

I have some more details about the issue.
Sometimes, the first error I get is:

‘Initialising Java Tooling’ has encountered a problem.
An internal error occurred during ‘Initialising Java Tooling.
assertion failed: Path for IClassPathEntry must be absolute: MYECLIPSE_LIB_HOME/1.4/activation/jar

This occurs when I first start eclipse.

Sometimes I don’t get that message, I get this one instead:

‘Building Workspace’ has encountered a problem
Errors during Build
Error instantiating builder ‘com.genuitec.eclipse.j2eedt.core.WebClassBuilder’.
Plug-in com.genuitec.eclipse.j2eedt.core was unable to load class com.genuitec.eclipse.j2eedt.core.builder.WebClasspathBuilder

Thereafter, every time I select any file in the Package Explorer, I get the error listed in my first post.

Finally, all ths only happens when I start eclipse after a reboot.
When I close down eclipse and reopen it, I get no errors at all ! ! !

Regards,

Aidan.

[Loyal Water]

Aidan,
Can you switch to a new workspace (File > Switch Workspace > Temp) and check if the problem persists? I get the feeling this is a workspace related issue.

[Aidan Hughes]

Hi,

Yes – the new worksace is not generating any errors.
I believe you are right – it’s a issue in my workspace.
Now – what’s the best way to import projects into my new workspace from the old one without hopefuloly picking up the same issue again?
Can you advise?

Thanks,

Aidan.

[Loyal Water]

Aidan,
You can switch to the new workspace and go to File > Import > General > Existing Project Into Workspace to import the projects into your new workspace. This should pick up the project without issues.

[Author]

Posts