Re: [wtr-general] Re: taza no longer works after upgrade to Ruby 1.8.7/ Watir 1.8.0

2011-03-23 Thread Željko Filipin
On Wed, Mar 23, 2011 at 2:34 AM, hillary weimar1...@gmail.com wrote:
 Now i'm running into another issue when i try to run the test

I have tried Taza recently and also had a lot of problems with it. It uses a
few gems that have really changed (active support, rspec...), and Taza got
only one small commit last year, nothing this year:

https://github.com/scudco/taza/commits/master/

If you want to get it working, I suggest that you take a look at a date when
the last Taza gem was released and then install all other required gems from
that time:

https://rubygems.org/gems/taza

Željko
--
watir.com - community manager
watir.com/book - author
viaqa.mobi conference on software testing - organizer
watirpodcast.com - host
testingpodcast.com - audio podcasts on software testing. all of them

-- 
Before posting, please read http://watir.com/support. In short: search before 
you ask, be nice.

watir-general@googlegroups.com
http://groups.google.com/group/watir-general
watir-general+unsubscr...@googlegroups.com


[wtr-general] Re: taza no longer works after upgrade to Ruby 1.8.7/ Watir 1.8.0

2011-03-23 Thread Chuck van der Linden
Try kicking out the current activesupport and installing an older
version of it.

I'm using the Watircraft framework, and when installing on a
Server2008R2 box (very much like Win7) I got similar errors when
trying to use the older ruby 1.8.6  where it wanted to run nmake etc

I ended up having to use Ruby 1.8.7 to get gems to install without
problems of that sort.

Removing the current activesupport gem, and specifically installing an
older version (I used 2.2.2) I was able to get things working for the
most part.  that prevented having to alter any of the scripts or
framework files due to the naming change, and all the AS stuff that is
used by Watir/Taza/Watircraft has been around for a LONG time, so it
doesn't require a 'current' version of that gem by any means.


On Mar 23, 2:16 am, Željko Filipin zeljko.fili...@wa-research.ch
wrote:
 On Wed, Mar 23, 2011 at 2:34 AM, hillary weimar1...@gmail.com wrote:
  Now i'm running into another issue when i try to run the test

 I have tried Taza recently and also had a lot of problems with it. It uses a
 few gems that have really changed (active support, rspec...), and Taza got
 only one small commit last year, nothing this year:

 https://github.com/scudco/taza/commits/master/

 If you want to get it working, I suggest that you take a look at a date when
 the last Taza gem was released and then install all other required gems from
 that time:

 https://rubygems.org/gems/taza

 Željko
 --
 watir.com - community manager
 watir.com/book - author
 viaqa.mobi conference on software testing - organizer
 watirpodcast.com - host
 testingpodcast.com - audio podcasts on software testing. all of them

-- 
Before posting, please read http://watir.com/support. In short: search before 
you ask, be nice.

watir-general@googlegroups.com
http://groups.google.com/group/watir-general
watir-general+unsubscr...@googlegroups.com


[wtr-general] Re: taza no longer works after upgrade to Ruby 1.8.7/ Watir 1.8.0

2011-03-22 Thread hillary
Okay. What's the best way to delete any references to ruby (either
1.8.6 or 1.8.7)? I'm going through the folder where I've installed
everything. But I'm not sure the best way to make sure that everything
is gone before trying to do a fresh install.


On Mar 22, 12:44 pm, Tim Koopmans tim.ko...@gmail.com wrote:
 Looks like you still have another version of Ruby on your system at c:/ruby

 If you're re-installing or changing versions, make sure you get rid of
 references to old binaries in your %PATH% especially for ruby and gem
 executables. Also delete any old ruby directories / gemfiles in your
 application / document settings path that may have not been cleaned up by
 the uninstall.

 If reinstalling from scratch I recommend using ruby 1.8.7 with the latest
 version of Watir.

 Pity you'r not on osx or linux as I'd definitely recommend RVM when
 'experimenting' with different ruby / gem versions =)

 Cheers,
 Tim

 @90kts

 On Wed, Mar 23, 2011 at 5:54 AM, hillary weimar1...@gmail.com wrote:
  So i've made a mess of my ruby/watir install. I was using taza with
  Ruby 1.8.6, Watir 1.6.7. and it worked. But then i was having trouble
  installing this configuration on a vm that i was setting up. Long
  story short I installed the latest version of watir/ruby on my local
  machine and its not working when i try to execute the taza commands to
  create a new site/pages/flows.

  I'd either like to be able to use the current installation or go back
  to the previous version that i had installed. For both of these
  options I'm running into problems.

  With the current configuration (Ruby 1.8.6/Watir 1.8.0), when I run
  this command:

  script\generate site insight

  I get the following error:

  C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:29:in
  `gem_original
  _require': no such file to load -- activesupport (LoadError)
         from C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/
  custom_require.rb:29:in
  `require'
         from C:/Ruby187/lib/ruby/gems/1.8/gems/taza-0.8.7/generators/
  site/site_g
  enerator.rb:3
         from C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/
  custom_require.rb:29:in
  `gem_original_require'
         from C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/
  custom_require.rb:29:in
  `require'
         from C:/Ruby187/lib/ruby/gems/1.8/gems/rubigen-1.5.6/lib/
  rubigen/spec.rb
  :16:in `klass'
         from C:/Ruby187/lib/ruby/gems/1.8/gems/rubigen-1.5.6/lib/
  rubigen/lookup.
  rb:165:in `instance'
         from C:/Ruby187/lib/ruby/gems/1.8/gems/rubigen-1.5.6/lib/
  rubigen/scripts
  /../scripts.rb:32:in `run'
         from script/generate:14

  Active support is installed, so I'm not sure what's happening.

  I've tried going to back to the previous version of Ruby/Watir but
  when i try to install any of the ruby gems I had I get an error
  message like this:

  Building native extensions.  This could take a
  while...
  ERROR:  Error installing
  rcov:
           ERROR: Failed to build gem native extenstion.

  c:/ruby/bin/ruby.exe
  creating
  Makefile

  nmake
  'nmake' is not recognized as an internal or external command, operable
  program or batch
  file.
  Gem files will remain installed in c:/ruby/lib/ruby/gems/1.8/gems/
  rcov-0.8.1.2.0 for
  inspection.
  Results logged to c:/ruby/lib/ruby/gems/1.8/gems/rcov-0.8.1.2.0/ext/
  rcovrt/gem_make.out

  System Information:
    Win7/32-bit
  RubyGems Environment:
   - RUBYGEMS VERSION: 1.6.2
   - RUBY VERSION: 1.8.7 (2011-02-18 patchlevel 334) [i386-mingw32]
   - INSTALLATION DIRECTORY: C:/Ruby187/lib/ruby/gems/1.8
   - RUBY EXECUTABLE: C:/Ruby187/bin/ruby.exe
   - EXECUTABLE DIRECTORY: C:/Ruby187/bin
   - RUBYGEMS PLATFORMS:
     - ruby
     - x86-mingw32
   - GEM PATHS:
      - C:/Ruby187/lib/ruby/gems/1.8
      - C:/Users/hhueter.CORP/.gem/ruby/1.8
   - GEM CONFIGURATION:
      - :update_sources = true
      - :verbose = true
      - :benchmark = false
      - :backtrace = false
      - :bulk_threshold = 1000
   - REMOTE SOURCES:
      -http://rubygems.org/

  Current gems installed:
  activesupport (3.0.5)
  builder (3.0.0)
  commonwatir (1.8.0)
  diff-lcs (1.1.2)
  firewatir (1.8.0)
  hoe (2.9.1)
  i18n (0.5.0)
  mocha (0.9.12)
  nokogiri (1.4.4.1 x86-mingw32)
  rake (0.8.7)
  rspec (2.5.0)
  rspec-core (2.5.1)
  rspec-expectations (2.5.0)
  rspec-mocks (2.5.0)
  rubigen (1.5.6)
  rubygems-update (1.3.6)
  s4t-utils (1.0.4)
  taglob (1.1.2)
  taza (0.8.7)
  user-choices (1.1.6.1)
  watir (1.8.0)
  win32-api (1.4.8 x86-mingw32)
  win32-process (0.6.5)
  windows-api (0.4.0)
  windows-pr (1.1.3)
  xml-simple (1.0.14)

  --
  Before posting, please readhttp://watir.com/support. In short: search
  before you ask, be nice.

  watir-general@googlegroups.com
 http://groups.google.com/group/watir-general
  watir-general+unsubscr...@googlegroups.com

-- 
Before posting, please read http://watir.com/support. In short: search before 
you ask, be nice.

watir-general@googlegroups.com

[wtr-general] Re: taza no longer works after upgrade to Ruby 1.8.7/ Watir 1.8.0

2011-03-22 Thread hillary
So I tried uninstalling everything and removing any reference to ruby,
and re-installing 1.8.7. and the rest of the gems. And I'm still
getting the same active support error when I try to generate a site.

On Mar 22, 12:44 pm, Tim Koopmans tim.ko...@gmail.com wrote:
 Looks like you still have another version of Ruby on your system at c:/ruby

 If you're re-installing or changing versions, make sure you get rid of
 references to old binaries in your %PATH% especially for ruby and gem
 executables. Also delete any old ruby directories / gemfiles in your
 application / document settings path that may have not been cleaned up by
 the uninstall.

 If reinstalling from scratch I recommend using ruby 1.8.7 with the latest
 version of Watir.

 Pity you'r not on osx or linux as I'd definitely recommend RVM when
 'experimenting' with different ruby / gem versions =)

 Cheers,
 Tim

 @90kts

 On Wed, Mar 23, 2011 at 5:54 AM, hillary weimar1...@gmail.com wrote:
  So i've made a mess of my ruby/watir install. I was using taza with
  Ruby 1.8.6, Watir 1.6.7. and it worked. But then i was having trouble
  installing this configuration on a vm that i was setting up. Long
  story short I installed the latest version of watir/ruby on my local
  machine and its not working when i try to execute the taza commands to
  create a new site/pages/flows.

  I'd either like to be able to use the current installation or go back
  to the previous version that i had installed. For both of these
  options I'm running into problems.

  With the current configuration (Ruby 1.8.6/Watir 1.8.0), when I run
  this command:

  script\generate site insight

  I get the following error:

  C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:29:in
  `gem_original
  _require': no such file to load -- activesupport (LoadError)
         from C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/
  custom_require.rb:29:in
  `require'
         from C:/Ruby187/lib/ruby/gems/1.8/gems/taza-0.8.7/generators/
  site/site_g
  enerator.rb:3
         from C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/
  custom_require.rb:29:in
  `gem_original_require'
         from C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/
  custom_require.rb:29:in
  `require'
         from C:/Ruby187/lib/ruby/gems/1.8/gems/rubigen-1.5.6/lib/
  rubigen/spec.rb
  :16:in `klass'
         from C:/Ruby187/lib/ruby/gems/1.8/gems/rubigen-1.5.6/lib/
  rubigen/lookup.
  rb:165:in `instance'
         from C:/Ruby187/lib/ruby/gems/1.8/gems/rubigen-1.5.6/lib/
  rubigen/scripts
  /../scripts.rb:32:in `run'
         from script/generate:14

  Active support is installed, so I'm not sure what's happening.

  I've tried going to back to the previous version of Ruby/Watir but
  when i try to install any of the ruby gems I had I get an error
  message like this:

  Building native extensions.  This could take a
  while...
  ERROR:  Error installing
  rcov:
           ERROR: Failed to build gem native extenstion.

  c:/ruby/bin/ruby.exe
  creating
  Makefile

  nmake
  'nmake' is not recognized as an internal or external command, operable
  program or batch
  file.
  Gem files will remain installed in c:/ruby/lib/ruby/gems/1.8/gems/
  rcov-0.8.1.2.0 for
  inspection.
  Results logged to c:/ruby/lib/ruby/gems/1.8/gems/rcov-0.8.1.2.0/ext/
  rcovrt/gem_make.out

  System Information:
    Win7/32-bit
  RubyGems Environment:
   - RUBYGEMS VERSION: 1.6.2
   - RUBY VERSION: 1.8.7 (2011-02-18 patchlevel 334) [i386-mingw32]
   - INSTALLATION DIRECTORY: C:/Ruby187/lib/ruby/gems/1.8
   - RUBY EXECUTABLE: C:/Ruby187/bin/ruby.exe
   - EXECUTABLE DIRECTORY: C:/Ruby187/bin
   - RUBYGEMS PLATFORMS:
     - ruby
     - x86-mingw32
   - GEM PATHS:
      - C:/Ruby187/lib/ruby/gems/1.8
      - C:/Users/hhueter.CORP/.gem/ruby/1.8
   - GEM CONFIGURATION:
      - :update_sources = true
      - :verbose = true
      - :benchmark = false
      - :backtrace = false
      - :bulk_threshold = 1000
   - REMOTE SOURCES:
      -http://rubygems.org/

  Current gems installed:
  activesupport (3.0.5)
  builder (3.0.0)
  commonwatir (1.8.0)
  diff-lcs (1.1.2)
  firewatir (1.8.0)
  hoe (2.9.1)
  i18n (0.5.0)
  mocha (0.9.12)
  nokogiri (1.4.4.1 x86-mingw32)
  rake (0.8.7)
  rspec (2.5.0)
  rspec-core (2.5.1)
  rspec-expectations (2.5.0)
  rspec-mocks (2.5.0)
  rubigen (1.5.6)
  rubygems-update (1.3.6)
  s4t-utils (1.0.4)
  taglob (1.1.2)
  taza (0.8.7)
  user-choices (1.1.6.1)
  watir (1.8.0)
  win32-api (1.4.8 x86-mingw32)
  win32-process (0.6.5)
  windows-api (0.4.0)
  windows-pr (1.1.3)
  xml-simple (1.0.14)

  --
  Before posting, please readhttp://watir.com/support. In short: search
  before you ask, be nice.

  watir-general@googlegroups.com
 http://groups.google.com/group/watir-general
  watir-general+unsubscr...@googlegroups.com

-- 
Before posting, please read http://watir.com/support. In short: search before 
you ask, be nice.

watir-general@googlegroups.com
http://groups.google.com/group/watir-general

Re: [wtr-general] Re: taza no longer works after upgrade to Ruby 1.8.7/ Watir 1.8.0

2011-03-22 Thread Tim Koopmans
Just delete the windows folders e.g. c:\ruby and cleanup any references in
%PATH% environment variable ...

Can't remember if there are also hidden folders for gemfiles in C:\documents
and settings\username

Sometimes that happens on networked PCs (i.e. in work setups)


Cheers,
Tim

@90kts



On Wed, Mar 23, 2011 at 8:48 AM, hillary weimar1...@gmail.com wrote:

 Okay. What's the best way to delete any references to ruby (either
 1.8.6 or 1.8.7)? I'm going through the folder where I've installed
 everything. But I'm not sure the best way to make sure that everything
 is gone before trying to do a fresh install.


 On Mar 22, 12:44 pm, Tim Koopmans tim.ko...@gmail.com wrote:
  Looks like you still have another version of Ruby on your system at
 c:/ruby
 
  If you're re-installing or changing versions, make sure you get rid of
  references to old binaries in your %PATH% especially for ruby and gem
  executables. Also delete any old ruby directories / gemfiles in your
  application / document settings path that may have not been cleaned up by
  the uninstall.
 
  If reinstalling from scratch I recommend using ruby 1.8.7 with the latest
  version of Watir.
 
  Pity you'r not on osx or linux as I'd definitely recommend RVM when
  'experimenting' with different ruby / gem versions =)
 
  Cheers,
  Tim
 
  @90kts
 
  On Wed, Mar 23, 2011 at 5:54 AM, hillary weimar1...@gmail.com wrote:
   So i've made a mess of my ruby/watir install. I was using taza with
   Ruby 1.8.6, Watir 1.6.7. and it worked. But then i was having trouble
   installing this configuration on a vm that i was setting up. Long
   story short I installed the latest version of watir/ruby on my local
   machine and its not working when i try to execute the taza commands to
   create a new site/pages/flows.
 
   I'd either like to be able to use the current installation or go back
   to the previous version that i had installed. For both of these
   options I'm running into problems.
 
   With the current configuration (Ruby 1.8.6/Watir 1.8.0), when I run
   this command:
 
   script\generate site insight
 
   I get the following error:
 
   C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:29:in
   `gem_original
   _require': no such file to load -- activesupport (LoadError)
  from C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/
   custom_require.rb:29:in
   `require'
  from C:/Ruby187/lib/ruby/gems/1.8/gems/taza-0.8.7/generators/
   site/site_g
   enerator.rb:3
  from C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/
   custom_require.rb:29:in
   `gem_original_require'
  from C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/
   custom_require.rb:29:in
   `require'
  from C:/Ruby187/lib/ruby/gems/1.8/gems/rubigen-1.5.6/lib/
   rubigen/spec.rb
   :16:in `klass'
  from C:/Ruby187/lib/ruby/gems/1.8/gems/rubigen-1.5.6/lib/
   rubigen/lookup.
   rb:165:in `instance'
  from C:/Ruby187/lib/ruby/gems/1.8/gems/rubigen-1.5.6/lib/
   rubigen/scripts
   /../scripts.rb:32:in `run'
  from script/generate:14
 
   Active support is installed, so I'm not sure what's happening.
 
   I've tried going to back to the previous version of Ruby/Watir but
   when i try to install any of the ruby gems I had I get an error
   message like this:
 
   Building native extensions.  This could take a
   while...
   ERROR:  Error installing
   rcov:
ERROR: Failed to build gem native extenstion.
 
   c:/ruby/bin/ruby.exe
   creating
   Makefile
 
   nmake
   'nmake' is not recognized as an internal or external command, operable
   program or batch
   file.
   Gem files will remain installed in c:/ruby/lib/ruby/gems/1.8/gems/
   rcov-0.8.1.2.0 for
   inspection.
   Results logged to c:/ruby/lib/ruby/gems/1.8/gems/rcov-0.8.1.2.0/ext/
   rcovrt/gem_make.out
 
   System Information:
 Win7/32-bit
   RubyGems Environment:
- RUBYGEMS VERSION: 1.6.2
- RUBY VERSION: 1.8.7 (2011-02-18 patchlevel 334) [i386-mingw32]
- INSTALLATION DIRECTORY: C:/Ruby187/lib/ruby/gems/1.8
- RUBY EXECUTABLE: C:/Ruby187/bin/ruby.exe
- EXECUTABLE DIRECTORY: C:/Ruby187/bin
- RUBYGEMS PLATFORMS:
  - ruby
  - x86-mingw32
- GEM PATHS:
   - C:/Ruby187/lib/ruby/gems/1.8
   - C:/Users/hhueter.CORP/.gem/ruby/1.8
- GEM CONFIGURATION:
   - :update_sources = true
   - :verbose = true
   - :benchmark = false
   - :backtrace = false
   - :bulk_threshold = 1000
- REMOTE SOURCES:
   -http://rubygems.org/
 
   Current gems installed:
   activesupport (3.0.5)
   builder (3.0.0)
   commonwatir (1.8.0)
   diff-lcs (1.1.2)
   firewatir (1.8.0)
   hoe (2.9.1)
   i18n (0.5.0)
   mocha (0.9.12)
   nokogiri (1.4.4.1 x86-mingw32)
   rake (0.8.7)
   rspec (2.5.0)
   rspec-core (2.5.1)
   rspec-expectations (2.5.0)
   rspec-mocks (2.5.0)
   rubigen (1.5.6)
   rubygems-update (1.3.6)
   s4t-utils (1.0.4)
   taglob (1.1.2)
   taza (0.8.7)
   user-choices (1.1.6.1)
   watir (1.8.0)
   win32-api 

[wtr-general] Re: taza no longer works after upgrade to Ruby 1.8.7/ Watir 1.8.0

2011-03-22 Thread hillary
Thanks. I did a fresh install after getting rid of everything. Got the
same issue after wards, it's because the scripts being called have a
require 'activesupport' and needed to be changed to require
'active_support'. So after editing the scripts i was able to generate
pages/flows/etc.

Now i'm running into another issue when i try to run the test. I get
this error:
C:\Users\username\Autorake spec:isolation:insight:blah_page --trace
(in C:/Users/username/Auto)
rake aborted!
no such file to load -- spec/rake/spectask
C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:29:in
`gem_original
_require'
C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:29:in
`require'
C:/Ruby187/lib/ruby/gems/1.8/gems/taza-0.8.7/lib/taza/tasks.rb:4
C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:32:in
`gem_original
_require'
C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:32:in
`require'
C:/Users/hhueter.CORP/Auto/rakefile:3
C:/Ruby187/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2383:in
`load'
C:/Ruby187/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2383:in
`raw_load_rakef
ile'
C:/Ruby187/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2017:in
`load_rakefile'

C:/Ruby187/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in
`standard_excep
tion_handling'
C:/Ruby187/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2016:in
`load_rakefile'

C:/Ruby187/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2000:in `run'
C:/Ruby187/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in
`standard_excep
tion_handling'
C:/Ruby187/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in `run'
C:/Ruby187/lib/ruby/gems/1.8/gems/rake-0.8.7/bin/rake:31
C:/Ruby187/bin/rake:19:in `load'
C:/Ruby187/bin/rake:19


On Mar 22, 4:51 pm, Tim Koopmans tim.ko...@gmail.com wrote:
 Just delete the windows folders e.g. c:\ruby and cleanup any references in
 %PATH% environment variable ...

 Can't remember if there are also hidden folders for gemfiles in C:\documents
 and settings\username

 Sometimes that happens on networked PCs (i.e. in work setups)

 Cheers,
 Tim

 @90kts

 On Wed, Mar 23, 2011 at 8:48 AM, hillary weimar1...@gmail.com wrote:
  Okay. What's the best way to delete any references to ruby (either
  1.8.6 or 1.8.7)? I'm going through the folder where I've installed
  everything. But I'm not sure the best way to make sure that everything
  is gone before trying to do a fresh install.

  On Mar 22, 12:44 pm, Tim Koopmans tim.ko...@gmail.com wrote:
   Looks like you still have another version of Ruby on your system at
  c:/ruby

   If you're re-installing or changing versions, make sure you get rid of
   references to old binaries in your %PATH% especially for ruby and gem
   executables. Also delete any old ruby directories / gemfiles in your
   application / document settings path that may have not been cleaned up by
   the uninstall.

   If reinstalling from scratch I recommend using ruby 1.8.7 with the latest
   version of Watir.

   Pity you'r not on osx or linux as I'd definitely recommend RVM when
   'experimenting' with different ruby / gem versions =)

   Cheers,
   Tim

   @90kts

   On Wed, Mar 23, 2011 at 5:54 AM, hillary weimar1...@gmail.com wrote:
So i've made a mess of my ruby/watir install. I was using taza with
Ruby 1.8.6, Watir 1.6.7. and it worked. But then i was having trouble
installing this configuration on a vm that i was setting up. Long
story short I installed the latest version of watir/ruby on my local
machine and its not working when i try to execute the taza commands to
create a new site/pages/flows.

I'd either like to be able to use the current installation or go back
to the previous version that i had installed. For both of these
options I'm running into problems.

With the current configuration (Ruby 1.8.6/Watir 1.8.0), when I run
this command:

script\generate site insight

I get the following error:

C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:29:in
`gem_original
_require': no such file to load -- activesupport (LoadError)
       from C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/
custom_require.rb:29:in
`require'
       from C:/Ruby187/lib/ruby/gems/1.8/gems/taza-0.8.7/generators/
site/site_g
enerator.rb:3
       from C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/
custom_require.rb:29:in
`gem_original_require'
       from C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems/
custom_require.rb:29:in
`require'
       from C:/Ruby187/lib/ruby/gems/1.8/gems/rubigen-1.5.6/lib/
rubigen/spec.rb
:16:in `klass'
       from C:/Ruby187/lib/ruby/gems/1.8/gems/rubigen-1.5.6/lib/
rubigen/lookup.
rb:165:in `instance'
       from C:/Ruby187/lib/ruby/gems/1.8/gems/rubigen-1.5.6/lib/
rubigen/scripts
/../scripts.rb:32:in `run'
       from script/generate:14

Active support is installed, so I'm not sure what's happening.

I've tried going