I had a merb.thor file and a src dir in my application that i have removed.
This is strange b/c a fresh app does not have this issue.  My app was
started with Merb 0.9.6 and i have tried to compare the two dirs for
differences and i don't see anything out of the ordinary.
Here's the stack of thor merb:gem:install:

/Users/michael/project/tasks/merb.thor/ops.rb:8:in `collect': undefined
method `root_path' for Thor::Tasks::Merb:Module (NoMethodError)
        from
/Users/michael/hhp/trebleNation2/tasks/merb.thor/main.thor:30:in
`initialize'
        from
/Library/Ruby/Gems/1.8/gems/thor-0.9.9/lib/thor/runner.rb:155:in `new'
        from
/Library/Ruby/Gems/1.8/gems/thor-0.9.9/lib/thor/runner.rb:155:in
`method_missing'
        from /Library/Ruby/Gems/1.8/gems/thor-0.9.9/lib/thor/task.rb:27:in
`send'
        from /Library/Ruby/Gems/1.8/gems/thor-0.9.9/lib/thor/task.rb:27:in
`run'
        from /Library/Ruby/Gems/1.8/gems/thor-0.9.9/lib/thor/task.rb:20:in
`parse'
        from /Library/Ruby/Gems/1.8/gems/thor-0.9.9/lib/thor.rb:78:in
`start'
        from /Library/Ruby/Gems/1.8/gems/thor-0.9.9/bin/thor:7
        from /usr/bin/thor:19:in `load'
        from /usr/bin/thor:19

Thanks,

Michael

On Tue, Feb 24, 2009 at 9:34 PM, Michael D'Auria
<[email protected]>wrote:

> I actually don't have a tasks/thor file, my tasks dir looks like:
> -rw-r--r--  1 michael  staff  4030 Nov  7 19:54 doc.thor
> drwxr-xr-x  8 michael  staff   272 Feb 24 20:47 merb.thor
>
> and merb.thor:
>
> -rw-r--r--  1 michael  staff   763 Feb 24 20:47 app_script.rb
> -rw-r--r--  1 michael  staff  1597 Feb 24 20:47 common.rb
> -rw-r--r--  1 michael  staff  3467 Feb 24 20:47 gem_ext.rb
> -rw-r--r--  1 michael  staff  4386 Feb 24 20:47 main.thor
> -rw-r--r--  1 michael  staff  2403 Feb 24 20:47 ops.rb
> -rw-r--r--  1 michael  staff   692 Feb 24 20:47 utils.rb
>
> When i run thor tasks, i see errors like:
>
> WARNING: unable to load thorfile "/Users/michael/project/tasks/doc.thor":
> Merb is not a module
> WARNING: unable to load thorfile
> "/Users/michael/project/tasks/merb.thor/main.thor": Merb is not a module
>
> Maybe i just need a thorfile?
>
> Thanks for your help,
>
> Michael
>
>
> On Tue, Feb 24, 2009 at 9:28 PM, Matt Aimonetti 
> <[email protected]>wrote:
>
>> you need to update the thor installer script:
>>
>> $ rm -rf tasks/thor
>> $ merb-gen thor
>>
>> And try again.
>>
>> - Matt
>>
>>
>> On Tue, Feb 24, 2009 at 6:13 PM, Michael D'Auria <
>> [email protected]> wrote:
>>
>>> I am not sure what I am supposed to do in order to bundle my gems.  I
>>> followed the guide here: http://wiki.merbivore.com/deployment/bundling,
>>> but the issue is that there is no merb:gem namespace any longer:
>>> $ thor merb:gem:install
>>> There was no available namespace `merb:gem'.
>>>
>>> I also tried merb:gems:install, but it complains that i called it
>>> incorrectly:
>>>
>>> $ thor merb:gems:install
>>> `install' was called incorrectly. Call as `install GEM_NAME [--binaries]
>>> [--version=VERSION] [--cache] [--merb-root=MERB_ROOT]'
>>>
>>> When i use the merb:dependencies:install i get a ton of errors:
>>>
>>> $ thor merb:dependencies:install
>>> Failed to install gem 'merb-core (= 1.0.9)' (undefined method `/' for
>>> nil:NilClass)
>>> Failed to install gem 'extlib (>= 0.9.8)' (undefined method `/' for
>>> nil:NilClass)
>>> Failed to install gem 'erubis (>= 2.6.2)' (undefined method `/' for
>>> nil:NilClass)
>>> Failed to install gem 'rake (>= 0)' (undefined method `/' for
>>> nil:NilClass)
>>> Failed to install gem 'json_pure (>= 0)' (undefined method `/' for
>>> nil:NilClass)
>>> ...
>>>
>>> Has anyone successfully bundled with version 1.0.9?
>>>
>>> Thanks,
>>>
>>> Michael
>>>
>>>
>>>
>>
>> >>
>>
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"merb" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/merb?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to