Bill Pugh wrote:
OK, what system are you trying to run on? What Eclipse version and what
OS version?
Running under Linux 2.6.11-6mdk Mandrake 10.2. Eclipse version
Version: 3.3.0
Build id: I20070503-1400
Using JDK 1.6.
We need to have a way to display HTML within Eclipse.
We first try to create a org.eclipse.swt.widgets.Composite.Browser.
If that doesn't work, we fall back to trying to create a
org.eclipse.jdt.internal.ui.text.HTMLTextPresenter.HTMLTextPresenter
(which is only available in Eclipse 3.2).
I'll fix the error msg so it logs the reason why it couldn't create a
Browser, which is what we really should be using.
That will be in tonights daily build, please try it tomorrow and see
what msg you get.
Well, the message has changed with your new build - here are all the
event details:
Message: Could not create a org.eclipse.swt.widgets.Composite.Browser
Stack Trace:
java.lang.RuntimeException: XPCOM error -2147221164
at
de.tobject.findbugs.view.DetailsView.createPartControl(DetailsView.java:188)
at
org.eclipse.ui.internal.ViewReference.createPartHelper(ViewReference.java:371)
at org.eclipse.ui.internal.ViewReference.createPart(ViewReference.java:227)
at
org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:592)
at org.eclipse.ui.internal.Perspective.showView(Perspective.java:2011)
at
org.eclipse.ui.internal.WorkbenchPage.busyShowView(WorkbenchPage.java:1017)
at org.eclipse.ui.internal.WorkbenchPage.access$17(WorkbenchPage.java:998)
at org.eclipse.ui.internal.WorkbenchPage$18.run(WorkbenchPage.java:3570)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
at org.eclipse.ui.internal.WorkbenchPage.showView(WorkbenchPage.java:3567)
at org.eclipse.ui.internal.WorkbenchPage.showView(WorkbenchPage.java:3543)
at
de.tobject.findbugs.FindbugsPlugin.showDetailsView(FindbugsPlugin.java:848)
at de.tobject.findbugs.FindbugsPlugin.showMarker(FindbugsPlugin.java:839)
at
de.tobject.findbugs.actions.MarkerRulerAction.update(MarkerRulerAction.java:189)
at
de.tobject.findbugs.actions.MarkerRulerAction.mouseDown(MarkerRulerAction.java:265)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:178)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1101)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3320)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2972)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2365)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2329)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2204)
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(EclipseAppLauncher.java:106)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.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(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:497)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:436)
at org.eclipse.equinox.launcher.Main.run(Main.java:1162)
Caused by: org.eclipse.swt.SWTError: XPCOM error -2147221164
at org.eclipse.swt.browser.Mozilla.error(Mozilla.java:1306)
at org.eclipse.swt.browser.Mozilla.create(Mozilla.java:408)
at org.eclipse.swt.browser.Browser.<init>(Browser.java:109)
at
de.tobject.findbugs.view.DetailsView.createPartControl(DetailsView.java:167)
... 39 more
Sessioneclipse.buildId=I20070503-1400
java.version=1.6.0_01
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_GB
Framework arguments: -startup
/home/rnc/eclipse/plugins/org.eclipse.equinox.launcher_1.0.0.v20070502.jar
Command-line arguments: -os linux -ws gtk -arch x86 -startup
/home/rnc/eclipse/plugins/org.eclipse.equinox.launcher_1.0.0.v20070502.jar
Data:
This was with MOZILLA_FIVE_HOME set. Digging into the above errors it
looked like eclipse was not picking up my firefox 2 installation
correctly. So after reading various sites I tried installing XULRunner
from http://developer.mozilla.org/en/docs/XULRunner and following its
installation instructions.
Unsetting MOZILLA_FIVE_HOME and rerunning shows that installing
XULRunner seems to have solved it.
Maybe this would be useful as a help entry somewhere?
Cheers
Nick
Bill
On May 21, 2007, at 9:39 AM, Nick Cross wrote:
Hi,
This does seem to be much better now - excellent! :-)
I am still getting however
java.lang.ClassNotFoundException:
org.eclipse.jdt.internal.ui.text.HTMLTextPresenter.HTMLTextPresenter
.....
at java.lang.Class.forName(Class.java:169)
at
de.tobject.findbugs.view.DetailsView.createPartControl(DetailsView.java:183)
at
org.eclipse.ui.internal.ViewReference.createPartHelper(ViewReference.java:371)
at
org.eclipse.ui.internal.ViewReference.createPart(ViewReference.java:227)
......
when clicking on a bug description with Eclipse latest milestone (M7).
Cheers
Nick
Bill Pugh wrote:
I haven't gotten any responses as to whether this seemed to solve the
problem.
I want to push out 1.2.1 within a week, so I'd appreciate feedback on
this.
Bill
On May 15, 2007, at 11:40 AM, Bill Pugh wrote:
OK, I committed something to head that seems to fix this,
at least for the scenario mentioned. This is now available
from
http://findbugs.cs.umd.edu/eclipse-daily
We actually want to do something smarter than just purging
the old bug from the bug collection, because we want the merging
to keep track of whether an issue is an old issue or a new issue.
There were some issues in the merging code, but I believe I have
addressed
those.
There may be other corner cases I've missed, please try it out and give
us your feedback.
Bill
On May 10, 2007, at 8:40 AM, Daniel Schneller wrote:
Ahhh... So this is not just me... I was wondering if I had screwed up
me workspace somehow but not bothered to create and configure a new
one. Good thing I didn't. Anyway I do not care that much, because I
usually just check the daily build logs for new bug markers and change
them "asynchronously".
Daniel
--Daniel Schneller
dannyschneller@xxxxxxxxxxx
http://jroller.com/page/dschneller - Java, MySQL, Windows, Linux and
other insanities.
_______________________________________________
Findbugs-discuss mailing list
Findbugs-discuss@xxxxxxxxxxxxxxxxxx
http://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss
_______________________________________________
Findbugs-discuss mailing list
Findbugs-discuss@xxxxxxxxxxxxxxxxxx
http://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss
_______________________________________________
Findbugs-discuss mailing list
Findbugs-discuss@xxxxxxxxxxxxxxxxxx
http://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss
|
