Some parts of this message have been removed.
Learn more about Nabble's
security policy.
On 10/4/07, sean.mcdirmid@... <sean.mcdirmid@...> wrote:
Maybe use 3.4 rather than 3.3? Eclipse does this to me also when
I'm debugging the plugin after a crash. Its just crazy, sometimes
it can't find any of my classes, but a second restart usually cleans
things up. Is there a crash involved?
Can you post here which Eclipse you use for your development - I think it would be helpful to separate issue between Eclipse versions and the functions of the plugin.
BTW: I cross post this to the tools list as it had been suggested that we use that for the plugin issues
This bug should be reported to the Eclipse people. This isn't
really a Scala plugin issue (well, as far as the Scala plugin is
designed to run on Eclipse goes...). I think the whole workspace
concept is kind of fragile, and they don't really store metadata
in a robust way. But Eclipse is the best thing we have right
now...
Quoting Andrew McGregor <mcgregorandrew@...>:
>
> On this problem, I've been getting something similar that is probably
> due to
> the Perforce plugin.
>
> To recover from this problem (which stops me starting Eclipse) I have to
> do:
>
> <path to eclipse>/eclipse -configuration file://tmp/e2.cfg
>
> A collegue has had success with
>
> <path to eclipse>/eclipse -clean
>
>
> Regards,
> Andrew.
>
>
> David Pollak-2 wrote:
> >
> >
> > Oh... and one more thing... 50% of the time when I start Eclipse, it
>
> > fails with:
> > Exception in thread "Thread-1" java.lang.NoClassDefFoundError
: Could
> not
> > initialize class org.eclipse.jface.preference.PreferenceConverter
> > at
> >
> org.eclipse.ui.internal.themes.ThemeElementHelper.installFont(ThemeElementHelper.java
:101)
> > at
> >
> org.eclipse.ui.internal.themes.ThemeElementHelper.populateRegistry (ThemeElementHelper.java:57)
> > at
> >
> org.eclipse.ui.internal.Workbench$28.runWithException
(Workbench.java:1426)
> > at
> >
> org.eclipse.ui.internal.StartupThreading$StartupRunnable.run (StartupThreading.java:31)
> > at
> org.eclipse.swt.widgets.RunnableLock.run
(RunnableLock.java:35)
> > at
> >
> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages( Synchronizer.java:123)
> > at
> > org.eclipse.swt.widgets.Display.runAsyncMessages
(Display.java:3296)
> > at
> > org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2974)
> > at
> org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2309)
> > at
> org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
> > at
> org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
> > at
> >
> org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
> > at
> >
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
> > at
> > org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> > at
> >
> org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
> > at
> >
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153)
> > at
> >
>
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication
(EclipseAppLauncher.java:
106)
> > at
> >
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start (EclipseAppLauncher.java:76)
> > at
> >
> org.eclipse.core.runtime.adaptor.EclipseStarter.run
(EclipseStarter.java:363)
> > at
> >
> org.eclipse.core.runtime.adaptor.EclipseStarter.run (EclipseStarter.java:176)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> > at
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java :39)
> > at
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
> > at java.lang.reflect.Method.invoke(Method.java:597)
> > at
> > org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:504)
> > at
org.eclipse.equinox.launcher.Main.basicRun(Main.java:443)
> > at org.eclipse.equinox.launcher.Main.run (Main.java:1169)
> >
> >
> > David Pollak wrote:
> >> I've got the plugin installed on a virgin version of Eclipse. I was
>
> >> editing /lift/ to make it compatible with the plugin. I got into a
>
> >> state where the compiler was stuck at 13%. I killed Eclipse after 40
>
> >> minutes and restarted. Now, Eclipse won't start and the console
> says:
> >> TYPE: 185872.0 ms 2-14462
> >> RECLAIM constructor User
> >> RECLAIM constructor Pet
> >> TYPE: 185878.0 ms 4-14463
> >> RECLAIM constructor User
> >> RECLAIM constructor Pet
> >> RECLAIM method dbTableName
> >> RECLAIM method dbTableName
> >> TYPE: 185895.0 ms 2-14464
> >> RECLAIM constructor User
> >> RECLAIM constructor Pet
> >> TYPE: 185902.0 ms 4-14465
> >> RECLAIM constructor User
> >> RECLAIM constructor Pet
> >> RECLAIM method dbTableName
> >> RECLAIM method dbTableName
> >> TYPE:
185908.0 ms 2-14466
> >> RECLAIM constructor User
> >> RECLAIM constructor Pet
> >> TYPE: 185929.0 ms 4-14467
> >> RECLAIM constructor User
> >> RECLAIM constructor Pet
> >> RECLAIM method dbTableName
> >> RECLAIM method dbTableName
> >> TYPE: 185935.0 ms 2-14468
> >> RECLAIM constructor User
> >> RECLAIM constructor Pet
> >> TYPE:
185942.0 ms 4-14469
> >> RECLAIM constructor User
> >> RECLAIM constructor Pet
> >> RECLAIM method dbTableName
> >> RECLAIM method dbTableName
> >> TYPE: 185958.0
ms 2-14470
> >> RECLAIM constructor User
> >> RECLAIM constructor Pet
> >> TYPE: 185965.0 ms 4-14471
> >> RECLAIM constructor User
> >> RECLAIM constructor Pet
> >> RECLAIM method dbTableNametf4554982.html#a13028023
> Sent from the Scala mailing list archive at
Nabble.com.
>
>
--
"How does it feel to be right all the time? - Terrible." (Mr Monk)
