1

I have a code snippet that is part of my eclipse plugin. When testing it in a runtime eclipse version (That means it is not packed into a jar afaik) it runs just fine.
However if I pack my plugin into a jar and then run the respective code snippet it results in a complete crash of eclipse without any error logs (I'm assuming that it even crashes the JVM).

I'm running this on Linux Mint.

According to this post the Desktop API is broken in older Java versions but it should be fixed in Java 8.
Has anyone an idea why this is still happening?

Community
  • 1
  • 1
Raven
  • 2,951
  • 2
  • 26
  • 42
  • Well, a library shouldn’t crash, but generally, it seems to be a contradiction to develop an Eclipse plugin using AWT instead of SWT. – Holger Jan 30 '17 at 10:24
  • My problem is that I haven't found another way to open a web page with the default browser... – Raven Jan 30 '17 at 16:32
  • Since Eclipse can do that, I’m quite sure that its API supports this… – Holger Jan 30 '17 at 16:33
  • Yes you were right. There is an API for that... I just had to explicitly search for one :) – Raven Jan 30 '17 at 20:20

1 Answers1

0

Although this is not an answer to the question why the Desktop API breaks down when used inside a jar file, I want to point out an alternative that I have found (thanks to @Holger) for my case (working with the eclipse APIs):

You can simply use PlatformUI.getWorkbench().getBrowserSupport().getExternalBrowser().openURL(<YourURL>); in order to open the given URL in the system's default browser.

Raven
  • 2,951
  • 2
  • 26
  • 42