Ah well, try again.
So, I was happily working with 0.9.34, upgraded to 0.9.35, lost
decorators. Recreated workspace, happy again.
Upgraded to 0.9.37, lost decorators. Recreated workspace, happy again.
Is there *anything* that I can do to work out what went wrong?
Is there anyone out there even getting this message?
Should I just stick with 0.9.37 and not do any more upgrades?
________________________________
From: Gary McWilliams [mailto:gary_mcwilliams@lagan.com]
Sent: 07 November 2005 14:07
To: users@subclipse.tigris.org
Subject: Upgrading loses svn decorators
During each recent subclipse upgrade, I lose the svn decorators from all
of my projects and files.
I've checked the Windows -> Preferences settings and they seem to be
fine.
I then have to re-create my workspace (from scratch) to get the
decorators back.
Am I doing something wrong? Is this something anyone else has come
across?
The 'default' installation for my new workspace uses JavaHL. I change it
to JavaSVN. In both cases the decorators work correctly in the new
workspace.
I tried changing this setting for a workspace in which the decorators
stopped showing, but it made no difference.
In the workspace that works (i.e. the newly created one), I am getting
the following exception (NOTE that everything seems to be working well):
!SESSION 2005-11-07 14:02:02.816
-----------------------------------------------
eclipse.buildId=M20050929-0840
java.version=1.5.0_04
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_GB
Command-line arguments: -data
D:\projects\svnroot\svnserver\v6-0-trunk\workspace -os win32 -ws win32
-arch x86
!ENTRY org.eclipse.osgi 2005-11-07 14:02:15.754
!MESSAGE While loading class
"org.tigris.subversion.svnclientadapter.commandline.Helper", thread
"Thread-2" timed out waiting (5000ms) for thread "Worker-1" to finish
starting bundle "org.tigris.subversion.subclipse.core". To avoid
deadlock, thread "Thread-2" is proceeding but
"org.tigris.subversion.svnclientadapter.commandline.Helper" may not be
fully initialized.
!STACK 0
java.lang.Exception: Generated exception.
at
org.eclipse.core.runtime.adaptor.EclipseClassLoader.findLocalClass(Eclip
seClassLoader.java:108)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(Bun
dleLoader.java:337)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLo
ader.java:389)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLo
ader.java:350)
at
org.eclipse.osgi.framework.adaptor.core.AbstractClassLoader.loadClass(Ab
stractClassLoader.java:78)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at
org.tigris.subversion.svnclientadapter.commandline.CommandLine$Character
StreamPumper.pumpStream(CommandLine.java:308)
at
org.tigris.subversion.svnclientadapter.commandline.CommandLine$StreamPum
per.run(CommandLine.java:245)
at java.lang.Thread.run(Unknown Source)
!ENTRY org.eclipse.osgi 2005-11-07 14:02:21.82
!MESSAGE While loading class
"org.tigris.subversion.subclipse.ui.console.SVNOutputConsole$2", thread
"main" timed out waiting (5000ms) for thread "Worker-1" to finish
starting bundle "org.tigris.subversion.subclipse.ui". To avoid deadlock,
thread "main" is proceeding but
"org.tigris.subversion.subclipse.ui.console.SVNOutputConsole$2" may not
be fully initialized.
!STACK 0
java.lang.Exception: Generated exception.
at
org.eclipse.core.runtime.adaptor.EclipseClassLoader.findLocalClass(Eclip
seClassLoader.java:108)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(Bun
dleLoader.java:337)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLo
ader.java:389)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLo
ader.java:350)
at
org.eclipse.osgi.framework.adaptor.core.AbstractClassLoader.loadClass(Ab
stractClassLoader.java:78)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at
org.tigris.subversion.subclipse.ui.console.SVNOutputConsole.createPage(S
VNOutputConsole.java:160)
at
org.eclipse.ui.internal.console.ConsoleView.doCreatePage(ConsoleView.jav
a:258)
at org.eclipse.ui.part.PageBookView.createPage(PageBookView.java:315)
at
org.eclipse.ui.part.PageBookView.partActivated(PageBookView.java:613)
at
org.eclipse.ui.internal.console.ConsoleView$1.run(ConsoleView.java:331)
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:3057)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2716)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:3
67)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143)
at
org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103)
at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActiva
tor.java:226)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:
376)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:
163)
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:334)
at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
at org.eclipse.core.launcher.Main.run(Main.java:973)
at org.eclipse.core.launcher.Main.main(Main.java:948)
In the workspace that no longer works (but that was working fine before
the upgrade), I get:
!SESSION 2005-11-07 13:58:09.487
-----------------------------------------------
eclipse.buildId=M20050929-0840
java.version=1.5.0_04
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_GB
Command-line arguments: -data
D:\projects\svnroot\svnserver\v6-0-trunk\workspace_311 -os win32 -ws
win32 -arch x86
!ENTRY org.eclipse.osgi 2005-11-07 13:58:25.487
!MESSAGE While loading class
"org.tigris.subversion.svnclientadapter.commandline.Helper", thread
"Thread-4" timed out waiting (5000ms) for thread "main" to finish
starting bundle "org.tigris.subversion.subclipse.core". To avoid
deadlock, thread "Thread-4" is proceeding but
"org.tigris.subversion.svnclientadapter.commandline.Helper" may not be
fully initialized.
!STACK 0
java.lang.Exception: Generated exception.
at
org.eclipse.core.runtime.adaptor.EclipseClassLoader.findLocalClass(Eclip
seClassLoader.java:108)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(Bun
dleLoader.java:337)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLo
ader.java:389)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLo
ader.java:350)
at
org.eclipse.osgi.framework.adaptor.core.AbstractClassLoader.loadClass(Ab
stractClassLoader.java:78)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at
org.tigris.subversion.svnclientadapter.commandline.CommandLine$Character
StreamPumper.pumpStream(CommandLine.java:308)
at
org.tigris.subversion.svnclientadapter.commandline.CommandLine$StreamPum
per.run(CommandLine.java:245)
at java.lang.Thread.run(Unknown Source)
!ENTRY org.eclipse.core.resources 2 1 2005-11-07 13:58:29.440
!MESSAGE Skipping builder
org.eclipse.cdt.managedbuilder.core.genmakebuilder for project
LocalMonitor. Either the builder is missing from the install, or it
belongs to a project nature that is missing or disabled.
The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this
message by anyone else is unauthorised. If you are not the intended
recipient, any disclosure, copying, or distribution of the message, or
any action or omission taken by you in reliance on it, is prohibited and
may be unlawful. Please immediately contact the sender if you have
received this message in error.
Received on Wed Nov 9 04:41:08 2005