problems with installing jspec

#112

I installed JSpec from github, like this:

$ sudo gem sources -a http://gems.github.com
http://gems.github.com added to sources
$ sudo gem install visionmedia-jspec
Successfully installed visionmedia-commander-3.3.0
Successfully installed visionmedia-jspec-2.0.3
2 gems installed

And now when I try to run the jspec script, I get:

/Library/Ruby/Gems/1.8/gems/visionmedia-jspec-2.0.3/bin/jspec:12: undefined method `program' for main:Object (NoMethodError)
        from /usr/bin/jspec:19:in `load'
        from /usr/bin/jspec:19

Reported by Jakub Suder · May 25th, 2009 @ 08:50 PM

Activity

ecin
Really odd deal going on here. Seems to have to do with requiring the commander v.3.3.0 gem which is available on github:
```
>> gem 'visionmedia-commander', '= 3.2.9'
=> true
>> require 'commander'
=> true
>> program
ArgumentError: wrong number of arguments (0 for 1)
```
Requiring either of those libraries alone doesn't seem to do the trick.
June 1st, 2009 @ 08:50 PM
ecin
And I take that back. The problem seems to be commander's v3.3.0 gem exclusively. So, uninstall it and install version 3.2.9 to get up and running.
```
gem uninstall visionmedia-commander 3.3.0
gem install visionmedia-commander --version '= 3.2.9' --source http://gems.github.com
```
June 1st, 2009 @ 08:56 PM
TJ Holowaychuk
- Milestone set to 3.0
- State changed from new to open
- Assigned user set to TJ Holowaychuk
Sorry about that guys, Github does not build gems based on tags (like I previously expected) so commander now has a corrupted build of 3.3.0. I will put this in the installation docs

June 3rd, 2009 @ 02:44 PM
TJ Holowaychuk
- State changed from open to resolved
June 19th, 2009 @ 03:20 PM

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.