- This topic has 3 replies, 3 voices, and was last updated 18 years, 3 months ago by Riyad Kalla.
-
AuthorPosts
-
zambizziMemberI’m just now catching up on my java projects at work and hadn’t tried 5.0 yet…was still running 4.1.1.
I just installed eclipse 3.2 and then used the installer I had downloaded about a month ago (5.0 GA) – I hadn’t noticed that there was a 5.0.1
Regardless, in 5.0 GA I’m not able to open a JSP w/ the visual editor – is this a known issue that requires me to move to 5.0.1? I get a simple dialog that says “An error has occurred, see the log for details”. In the log I see this:
!ENTRY org.eclipse.jface 4 2 2006-10-04 14:01:09.937 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface". !STACK 0 java.lang.NoClassDefFoundError: com/genuitec/javascript/debug/mozilla/ImprovedMozillaBrowser at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Unknown Source) at java.lang.Class.getConstructor0(Unknown Source) at java.lang.Class.newInstance0(Unknown Source) at java.lang.Class.newInstance(Unknown Source) at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:157) at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:759) at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243) at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:51) ...........
Will I have to entirely re-install to get to 5.0.1 or is there an update in the update manager for me?
Thanks!
padyalaMemberHi,
Iam also getting the same error did you get any resolution for this error.
Thanks
Partha
zambizziMemberNo, not yet. I’m just starting fresh. I uninstalled 5.0 GA and am installing eclipse 3.2.1 and myeclipse 5.0.1 – hopefully this will take care of business. I’ll keep you posted.
Riyad KallaMemberSorry you guys ran into this, just restart using the -clean command line argument to get around this issue. We thought we had it fixed in 5.0.1 (forces a restart with -clean after install).
-
AuthorPosts