Hmmm... Now that I know what to google for: Their code already is pretty smart about the location of firefox-bin, and they have special code for Ubuntu and OSX:
http://svn.openqa.org/fisheye/browse/~raw,r=2073/selenium-rc/trunk/server-coreless/src/main/java/org/openqa/selenium/server/browserlaunchers/FirefoxChromeLauncher.java Probably it's just a matter of waiting for the next release of Selenium and the corresponding Maven plugin. On Jan 14, 2008 8:52 PM, Jesse Kuhnert wrote: > p.s. This is documented "somewhere" in Selenium already - but it's > possible that this deserves a bug report on that project as well. If > they are executing a new process via the java Runtime class then I > know it shouldn't be very hard for them to parse standard err / out > and detect if the browser they are looking for doesn't exist and > report it appropriately to standard error for the main process if that > is the case. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
