That's true. Correct me if I'm wrong, but for IE, it's just a matter of regsrv32 with the ocx. I remember in the old days, installing an FF plugin was as simple as copying a file. This is not really GWT specific, more for the gwt-maven guys, but it would be nice if the plugin could provision browsers.
-Ray On Fri, Nov 21, 2008 at 10:36 AM, John Tamplin <[EMAIL PROTECTED]> wrote: > On Fri, Nov 21, 2008 at 12:40 PM, Ray Cromwell <[EMAIL PROTECTED]> > wrote: >> >> It would also require a patch to the maven plugin to allow it to >> download and install the OOPHM browser plugins, otherwise, the 'clean >> checkout test run' scenario won't work. So the plugins should be >> bundled as a separate artifact in the repo, downloadable via a maven >> plugin. A goal to launch a selenium server would be cool too. My >> goals are to avoid having the person build stuff do any configuration >> for it to work. > > It isn't clear how the browser plugins would get installed without any user > interaction on all platforms, however. To run selenium in FF, you need to > create a new profile with the plugin installed. A profile could be checked > in, but it would likely be very vulnerable to browser version differences. > > -- > John A. Tamplin > Software Engineer (GWT), Google > > > > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
