Recent changes to bugs

NullPointerException due to missing mrj.version on Mac OS X Sierra (10.12.5)

Andrew Wheelwright — Thu, 20 Jul 2017 05:21:26 -0000

I recently came across BrowserLauncher2 while looking for a platform independant mechanism for opening a default browser with more reliability than the java.awt.Desktop API provides.

Unfortunately it doesn't work on Mac OS X Sierra (10.12.5). The BrowserLaunching factory assumes the existence of the mrj.version system property which is not defined. Running java -XshowSettings:properties confirms the property isn't there. The subsequent attempt to call substring on the result of the System.getProperty call throws a NullPointerException, killing the application at that point.

Browserlauncher doesn't see firefox.exe

Joop — Fri, 30 Dec 2016 14:52:47 -0000

OS: OS/2-eCS version 1.2 (working goes from 1.0 up to 2.2)
Java: OpenJDK Version 1.6.0 Build 27 (our latest)
Java program: BrowserLauncher2-1_3.jar
Bugs:
edu.stanford.ejalbert.exception.BrowserLaunchingInitializingException: one of the supported browsers must be installed: FireFox; Epiphany; Konqueror; Netscape; Opera; Mozilla; FireFox
at edu.stanford.ejalbert.launching.misc.UnixNetscapeBrowserLaunching.initialize(UnixNetscapeBrowserLaunching.java:200)
at edu.stanford.ejalbert.BrowserLauncher.initBrowserLauncher(BrowserLauncher.java:240)
at edu.stanford.ejalbert.BrowserLauncher.<init>(BrowserLauncher.java:216)
at edu.stanford.ejalbert.BrowserLauncher.<init>(BrowserLauncher.java:177)
at edu.stanford.ejalbert.BrowserLauncher.main(BrowserLauncher.java:274)

Setup:
java -Duser.home=drive:\utils\browserlauncher -jar BrowserLauncher2-1_3.jar drive:\firefox_3880\firefox.exe 2>browserlauncher-bugs-txt

Also tried:
java -Dbrowser.cmd="drive:\firefox_3880\firefox.exe" -Dbrowser.arg0="$url" -Duser.home=drive:\utils\browserlauncher -jar BrowserLauncher2-1_3.jar 2>browserlauncher-bugs-txt

drive: is in real a driveletter.

As every OS is going a different direction you get the problem that you can't adress a general setup. Why just not ask in the setup where the browser is, looks to me the most simple solution. Next solution is the argument -Dbrowser.cmd with -Dbrowser.arg0. But both are not implemented in a system which is designed to program once and run everywhere.
Next the problems of what is called "dll-hell". Every OS gets its share in this. We have the problem of libs ported from Unix with diferent setups. OS/2 can run next to each other, no problem, but has to be instructed to do so. This is done with a small kickoff program which starts the browser and is transparent to the browser but do set a few things right so ohter programs don't have a problem.
As many developers make use of your system its most east to put in both methods, one ask for it, two if oen is not possible with the arguments.
This would solve a lot of problems. Thanks.

#12 Missing Properties File in Maven JAR

Killerbee — Mon, 31 Oct 2016 19:32:43 -0000

can confirm this problem. Easiest workaround is:

<dependency>
<groupId>edu.stanford.ejalbert</groupId>
<artifactId>BrowserLauncher2</artifactId>
<version>1.3</version>
</dependency>
<dependency>
<groupId>edu.stanford.ejalbert</groupId>
<artifactId>BrowserLauncher2</artifactId>
<version>1.3</version>
<classifier>sources</classifier>
</dependency>

To also get the property files ;)

Missing Properties File in Maven JAR

Andre Beckus — Mon, 08 Dec 2014 02:42:12 -0000

I had an issue using the jar file in the Maven repository. I used this dependency tag:
<dependency>
<groupId>edu.stanford.ejalbert.test</groupId>
<artifactId>BrowserLauncher2</artifactId>
<version>1.3</version>
</dependency>

The application built successfully, but when I ran it, I received an error saying that the "/edu/stanford/ejalbert/launching/misc/linuxUnixConfig.properties" file could not be read. When I looked in the jar from Maven, I found that this file was indeed missing. I looked in the jar downloaded from the Sourceforge project site and the properties file was there. My workaround was to manually install the Sourceforge jar into my local Maven repository.

NPE with Oracle 1.7u4 JDK under Mac OS X 10.7

Sylvain LAFRASSE — Tue, 15 May 2012 19:13:15 -0000

The fix:
// Handle BrowserLuancher NPE when running under Oracle 1.7u4 release for Mac OS X
final String mrjVersionSystemProperty = System.getProperty("mrj.version");
if (mrjVersionSystemProperty == null) {
System.setProperty("mrj.version", "999.999");
}

URL containing white spaces are not opened on Mac

tiberiu — Wed, 07 Sep 2011 06:01:09 -0000

Hi,

As mentioned by several users both on the Forum and into the Tracker it seems that files/URLs that contain empty spaces in their full path do not open on MAC OS platforms. It there a solution for this?

Tibi

BrowserLauncher 1.3 choses wrong browser for default

Klaue — Thu, 28 Jan 2010 03:16:18 -0000

On Ubuntu 9.10, using the normal
BrowserLauncher launcher = new BrowserLauncher();
launcher.openURLinBrowser("http://google.com/");
opens the adress using Epiphany instead of my default, firefox
Manually choosing firefox works as it should.

Note: It worked as it should using BrowserLauncher 1.2 (I guess that was the version I had), to which I'm now reverting.

Class: WindowsBrowserLaunching

Anonymous — Wed, 29 Aug 2007 22:28:44 -0000

This project fails when the full path to the file that supposed to be shown contents signs such “$”, because the function “replaceAll()” translates this “$” sign as the end of a line.

Class:
WindowsBrowserLaunching
Function:
private String[] getCommandArgs(String protocol, String urlString) {

Bug in the line:
String commandArgs = commandsDefaultBrowser.replaceAll("<url>", urlString);

BrowserLauncherRunner no longer public

Tristan Richard — Thu, 19 Apr 2007 20:52:31 -0000

As of v1.0, BrowserLauncherRunner is not public anymore, so we cannot use it with the recommanded syntax:

BrowserLauncherErrorHandler errorHandler = new TestAppErrorHandler(debugTextArea);
BrowserLauncherRunner runner = new BrowserLauncherRunner(launcher, urlString, errorHandler);
Thread launcherThread = new Thread(runner);
launcherThread.start();

I had to downgrade to 1.0RC4 for this to work.

Firefox window did not open

Johann-Nikolaus Andreae — Wed, 21 Mar 2007 14:25:34 -0000

I had truble with jUploadr witch use BrowserLauncher2 to open the browser window for authorization. So i search for the reason.
I found out that ther a problem with firefox -remote openURL(<url>). on the console only firefox -remote "openURL(<url>)" works. i have change i in the linuxUnixConfig.properties to <browser> -new-tab <url> (like konqueror) an now it woks.

I did not now witch firefox versions affected but is seams tha i not the only one with this problem
http://juploadr.sourceforge.net/2006/04/17/authorization-failed/