[ervharl]

I’m running a trial version of MyEclipese Enterprice Workbench Version: 5.1.0 GA Build id: 20061111-5.1.0-GA with Eclipse 3.2.1
When I start the application I get an “Unable to locate .myeclipse.properties file” message.
When right-clicking on any node in the explorer tree I get the two errors:
* Unhandled event loop exception
With Exception Stack Trace:
<
An exception stack trace is not available.
>

and

* org/eclipse/wst/sse/ui/internal/reconcile/validator/ValidationHelper
With Exception Stack Trace:
<
java.lang.NoClassDefFoundError: org/eclipse/wst/sse/ui/internal/reconcile/validator/ValidationHelper
at com.genuitec.myeclipse.ui.action.ExcludeFromValidationActionDelegate.isEnabled(ExcludeFromValidationActionDelegate.java:212)
at com.genuitec.myeclipse.ui.action.ExcludeFromValidationActionDelegate.selectionChanged(ExcludeFromValidationActionDelegate.java:196)
at org.eclipse.ui.internal.PluginAction.refreshEnablement(PluginAction.java:208)
at org.eclipse.ui.internal.PluginAction.selectionChanged(PluginAction.java:280)
at org.eclipse.ui.internal.ObjectActionContributor.contributeObjectActions(ObjectActionContributor.java:144)
at org.eclipse.ui.internal.ObjectActionContributorManager.contributeObjectActions(ObjectActionContributorManager.java:96)
at org.eclipse.ui.internal.PopupMenuExtender.addObjectActions(PopupMenuExtender.java:253)
at org.eclipse.ui.internal.PopupMenuExtender.menuAboutToShow(PopupMenuExtender.java:315)
at org.eclipse.jface.action.MenuManager.fireAboutToShow(MenuManager.java:289)
at org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:395)
at org.eclipse.jface.action.MenuManager.access$1(MenuManager.java:391)
at org.eclipse.jface.action.MenuManager$2.menuShown(MenuManager.java:417)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:117)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:952)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:933)
at org.eclipse.swt.widgets.Control.WM_INITMENUPOPUP(Control.java:3556)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:3272)
at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1539)
at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:1634)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4025)
at org.eclipse.swt.internal.win32.OS.TrackPopupMenu(Native Method)
at org.eclipse.swt.widgets.Menu._setVisible(Menu.java:225)
at org.eclipse.swt.widgets.Display.runPopups(Display.java:3374)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2962)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
at org.eclipse.core.launcher.Main.run(Main.java:977)
at org.eclipse.core.launcher.Main.main(Main.java:952)
>

[Riyad Kalla]

The right-clicking is a problem we are tracking down now (reported here: http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-15011-start-15.html) that pertains to using MyEclipse 5.1 ontop of an existing Eclipse install that includes portions of WTP on it. The workaround, at this moment, is a clean reinstall of MyEclipse using the All-In-One installer for Windows (Easiest) or just performing a clean install of Eclipse + MyEclipse yourself.

Please see the other thread for updates and followups, we are sorry for this initial impression. In our internal testing of upgrading all our test machines, they went smoothly. But we may have missed possible combinations from the numerous projects available from the Callisto update site, so there are some users getting effected by this.

[ervharl]

Thanks Riyad ,

what about the “Unable to locate .myeclipse.properties file” message?
When can we expect a correction package on the WTP-problem?

/Harald

P.S. It seems like that the link http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-15011-start-15.html is broken.

[Riyad Kalla]

what about the “Unable to locate .myeclipse.properties file” message?

You can manually create the file, but the warning is actually harmless. That is just a global file used to store your subscription information so you don’t need to enter it into each workspace you work with. If it can’t create this file, it just falls back to storing the information in your workspace.

When can we expect a correction package on the WTP-problem?

We narrowed down one of the problems and have updated the update site to fix it. Unfortunately if users have manually installed WST and JST outside of MyEclipse, then upgrade to 5.1, what happens is the Eclipse platform is loading the normal JST/WST versions which breaks MyEclipse 5.1 because we had to modify the WST just a hair to support our new exclusion functionality.

The workaround is to erase the JST/WST plugins from your Eclipse/plugins dir and let MyEclipse loads it’s own.

[ervharl]

So, if I’ve got i right, the workaround is to make a clean install of Eclipse and MyEclipse, and after that install Callisto wthout any limitations?

/Harald

[Riyad Kalla]

Harald,
I am not 100% positive if the “afterwards, Callisto is fine” is accurate. Just don’t install JST/WST from the Callisto Discovery site and you should be OK. We are shipping WTP 1.5.2 anyway, so you have all the dependencies for your own plugins and it shouldn’t break anything.

We had a few users tell us that with a broken install, if they just removed JST/WST from Eclipse/plugins dir, letting the MyEclipse copies load, everything was fine.

** UPDATE, I just tried the new update site we rolled out, and it has fixed the problem with JST/WST. You should be fine to use the update manager “normally” now.

[Author]

Posts