Additional info and fix: The issue lied in browser.rb:activate_gem gem_name and the directory structure:
watir-1.6.2/lib/watir/ After moving everything from lib/watir to lib things work great. On Mar 5, 11:06 am, Cliff <[email protected]> wrote: > Hello Group > > Has anybody tried running watir installed to a non-default gem system > path? For example, assuming you've installed all required gems using > something like: > > gem install <gem> --no-rdoc --no-ri --ignore-dependencies -i /temp/ > gems > > Then in irb: > require 'rubygems' > Gem.clear_paths > ENV['GEM_HOME'] = "\temp\gems" > ENV['GEM_PATH'] = "\temp\gems" > > require 'watir' > Watir::options = {:browser => 'ie'} > Watir::Browser.new ----> NameError: (eval):1:in `klass': uninitialized > constant Watir::IE > > Note, with this setup if :browser => 'firefox' the Watir::Browser.new > opens firefox as expected. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Watir General" group. To post to this group, send email to [email protected] Before posting, please read the following guidelines: http://wiki.openqa.org/display/WTR/Support To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/watir-general -~----------~----~----~----~------~----~------~--~---
