There is an error message in the log related to subclipse, but it
occurred around 12:30 today and our problems with subclipse only started
a couple of hours after that. I have restarted Eclipse to see if it is
a startup error that is causing problems later with no luck. If I move
the log file to a new location, the log file remains empty even after
several 'Show in Resource History' attempts.
Here is the last error in the Eclipse .log file (earlier errors were
from previous days). It seems fairly benign, a timeout on startup:
!SESSION 2006-07-25 12:36:10.042
-----------------------------------------------
eclipse.buildId=M20060629-1905
java.version=1.5.0_07
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86
!ENTRY org.eclipse.osgi 4 0 2006-07-25 12:36:34.776
!MESSAGE While loading class
"org.tigris.subversion.subclipse.ui.console.ConsoleDocument$ConsoleLine"
, thread "main" ti
med 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.ConsoleDocument$ConsoleLine"
may
not be fully initialized.
!STACK 0
java.lang.Exception: Generated exception.
at
org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.preFindLoca
lClass(EclipseLazyStarter.java:75)
at
org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(Clas
spathManager.java:409)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(
DefaultClassLoader.java:188)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(Bun
dleLoader.java:339)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLo
ader.java:391)
at
org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLo
ader.java:352)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(Defau
ltClassLoader.java:83)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at
org.tigris.subversion.subclipse.ui.console.ConsoleDocument.getLines(Cons
oleDocument.java:79)
at
org.tigris.subversion.subclipse.ui.console.SVNOutputConsole.dump(SVNOutp
utConsole.java:202)
at
org.tigris.subversion.subclipse.ui.console.SVNOutputConsole.access$1(SVN
OutputConsole.java:199)
at
org.tigris.subversion.subclipse.ui.console.SVNOutputConsole$1.run(SVNOut
putConsole.java:124)
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:3325)
at
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2971)
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:4
19)
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(PlatformActiva
tor.java:78)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplicat
ion(EclipseAppLauncher.java:92)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Eclip
seAppLauncher.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(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
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)
-----Original Message-----
From: Mark Phippard [mailto:markp@softlanding.com]
Sent: Tuesday, July 25, 2006 3:45 PM
To: users@subclipse.tigris.org
Subject: Re: [Subclipse-users] Resource history blank, cmdline tools see
history
"Chris Audley" <chris.audley@beacon-cs.com> wrote on 07/25/2006 03:20:04
PM:
> Today we had a problem with our subversion repository and it had to be
> repaired with db_recover. Afterward, 'Team->Show in Resource History'
> will display an empty 'Resource History' view on every file we've
tried.
> The command line tools will display a log of the file with no
problems.
>
> This is using Subclipse 1.0.3 with Eclipse 3.2. Incidentally, we had
> tried 1.1.2 with Eclipse 3.2 but abandon it because the new 'History'
> view was showing an empty history for every file. We assumed that was
> due to bugs in the development subclipse and rolled back.
>
> We have tried both JavaSVN and JavaHL with the same results. We have
> also tried deleting the projects and checking them out from subversion
> again. The 'Show Annotation' feature works, but without the history
> visible. Why can't subclipse see the history when the command line
> clearly can?
Check the Eclipse error log and see if any kind of exception was logged.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Tue Jul 25 21:58:04 2006