Looking further, it looks like an issue in rubygems_plugin.rb Namely, the call to add_option within initialize.
It looks like that should take a block. Otherwise, I hit the errors mentioned below when rubygems attempts to parse the arguments If its working on your end with arguments, is it possible you have an updated version of rubygems_plugin.rb ? Best Regards, Kevin On Wed, Oct 14, 2009 at 12:01 PM, Kevin Radcliffe <kevin.radcli...@gmail.com> wrote: > James, > I've installed using gem and igem without issue, but when I attempt > to run torture, it doesn't seem to be properly recognized > if I specify a public path. Is there anything special I need to do > with the path?: > >>gem torture --public TestIMApp1 > ERROR: While executing gem ... (NoMethodError) > undefined method `call' for nil:NilClass > >>igem torture --public TestIMApp1 > ERROR: While executing gem ... (NoMethodError) > undefined method `call' for nil:NilClass > > However, if I manually create a directory called "public", then I can > run without any arguments and it seems to setup up appropriately: > >>mkdir public > >>igem torture > #Setup message displays properly here. > > Best Regards, > Kevin > > On Wed, Oct 14, 2009 at 11:17 AM, Web Administrator <webad...@nobts.edu> > wrote: >> I just pushed v0.2.0 of a gem I have put together called iron_maiden to >> gemcutter. >> >> Github: http://github.com/jwthompson2/iron_maiden >> Gemcutter: http://gemcutter.org/gems/iron_maiden >> >> It has a basic IronRuby.Rack template that it will copy into an app via the >> `gem torture` command. >> >> It is still quite rough and mostly untested. >> >> I'd love feedback. >> >> >> Thanks, >> James Thompson >> >> _______________________________________________ >> Ironruby-core mailing list >> Ironruby-core@rubyforge.org >> http://rubyforge.org/mailman/listinfo/ironruby-core >> >> > _______________________________________________ Ironruby-core mailing list Ironruby-core@rubyforge.org http://rubyforge.org/mailman/listinfo/ironruby-core
