Community
Participate
Working Groups
I have some projects that I pulled in from svn and renamed to group them together. Even though all have project-id defined, the references show up as ?. It seems that some of the code must still be referring to the project-id.
NOt sure what you mean exactly by confused and where the ? is showing up. Also references are made by modelID, not projectID.
Would this be related to the fact that Tigerstripe doesn't use resource changes properly? To validate that, a restart of Eclipse and project clean would be a work-around.
I think this may have been caused by a crash somewhere - seems to be working today From yesterday's log java.lang.NullPointerException at org.eclipse.tigerstripe.workbench.internal.api.impl.TigerstripeProjectHandle.addModelReference(TigerstripeProjectHandle.java:315) at org.eclipse.tigerstripe.workbench.ui.internal.editors.descriptor.dependencies.ReferencedProjectsSection.addButtonSelected(ReferencedProjectsSection.java:251) at org.eclipse.tigerstripe.workbench.ui.internal.editors.descriptor.dependencies.ReferencedProjectsSection$1.widgetSelected(ReferencedProjectsSection.java:180) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) 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:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) 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:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
This problem fixed.
