Q7

Not enough information when Q7 cannot clear workspace

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.2.0
  • Fix Version/s: 1.3.8
  • Component/s: Runtime
  • Labels:
    None
  • Test Mode:
    Manual

Description

When WorkspaceContext cannot delete a project (i.e. project.delete throws CoreException), we do not preserve (or do not include into a report) an information from caught exception, therefore it is hard to understand underlying reasons.

Eclipse Status {
    severity: ERROR
    message: Failed to apply context "empty_workspace" caused by: Problems encountered while deleting resources.
    plugin: com.xored.q7.core
    exception: org.eclipse.core.runtime.CoreException: Failed to apply context "empty_workspace" caused by: Problems encountered while deleting resources.
      at com.xored.q7.ctx.resources.WorkspaceContextProcessor.removeWorkspaceFiles(WorkspaceContextProcessor.java:192)
      at com.xored.q7.ctx.resources.WorkspaceContextProcessor.access$1(WorkspaceContextProcessor.java:177)
      at com.xored.q7.ctx.resources.WorkspaceContextProcessor$8$1.run(WorkspaceContextProcessor.java:162)
      at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344)
      at com.xored.q7.ctx.resources.WorkspaceContextProcessor$8.run(WorkspaceContextProcessor.java:159)
      at com.xored.q7.internal.runtime.ui.UIRunnable$1.doProcessing(UIRunnable.java:62)
      at com.xored.tesla.swt.events.TeslaEventManager.doProcessing(TeslaEventManager.java:104)
      at com.xored.tesla.swt.aspects.DisplayAspect.ajc$around$com_xored_tesla_swt_aspects_DisplayAspect$1$e269b158(DisplayAspect.aj:74)
      at org.eclipse.swt.widgets.Display.sleep(Display.java:4646)
      at org.eclipse.ui.application.WorkbenchAdvisor.eventLoopIdle(WorkbenchAdvisor.java:364)
      at org.eclipse.ui.internal.ide.application.IDEWorkbenchAdvisor.eventLoopIdle(IDEWorkbenchAdvisor.java:917)
      at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2702)
      at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665)
      at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499)
      at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679)
      at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
      at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668)
      at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
      at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
      at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-2)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      at java.lang.reflect.Method.invoke(Method.java:601)
      at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
      at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
      at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
      at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
  }
} 

Activity

There are no comments yet on this issue.

People

Vote (0)
Watch (0)

Dates

  • Created:
    23/Aug/13 4:25 PM
    Updated:
    03/Oct/13 10:16 AM
    Resolved:
    03/Oct/13 10:16 AM