search

zhenyajiang / jupiter-eclipse-plugin

Automatically exported from code.google.com/p/jupiter-eclipse-plugin
0 stars 0 forks source link

Jupiter fails to work with Windows paths containing "\u" #28

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
In Windows if the user has a workspace path containing "\u" (or maybe this
is the case for all escape characters) Jupiter will fail to work properly.
 Most commonly exceptions are shown in the log file and the user is not
able to add any issues.

This issue is Windows specific as Linux and OSX don't use the same slashes
for their paths.

Here is one of the exceptions:
!ENTRY org.eclipse.ui 4 0 2008-05-15 23:58:02.930
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.NullPointerException
    at
edu.hawaii.ics.csdl.jupiter.util.ReviewDialog.processNonReviewIdNotificationDial
og(ReviewDialog.java:48)
    at
edu.hawaii.ics.csdl.jupiter.util.ReviewDialog.processReviewIdSelectionWizardDial
og(ReviewDialog.java:153)
    at
edu.hawaii.ics.csdl.jupiter.ui.action.ReviewAdditionActionDelegate.determineProj
ectReviewIdReviewerId(ReviewAdditionActionDelegate.java:168)
    at
edu.hawaii.ics.csdl.jupiter.ui.action.ReviewAdditionActionDelegate.run(ReviewAdd
itionActionDelegate.java:81)
    at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:256)
    at
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionCont
ributionItem.java:545)
    at
org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.
java:490)
    at
org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContribution
Item.java:402)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
    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(Ecli
pseAppLauncher.java:106)
    at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLau
ncher.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(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    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)

Original issue reported on code.google.com by jsakuda on 16 May 2008 at 10:05

GoogleCodeExporter commented 8 years ago 
Ignore the exception pasted above.  It turns out that it is not related to this 
issue.

Original comment by jsakuda on 16 May 2008 at 11:14

GoogleCodeExporter commented 8 years ago 
I don't think this is a problem.  There is a problem but this isn't it.

Original comment by jsakuda on 21 May 2008 at 1:37