When I try to bundle a slice using the steps Jacques describes for
bundling non-public gems, I get:
$ bin/thor merb:gem:install
Beginning transaction
/srv/http/wotr.topfans.com/production/tasks/merb.thor/gem_ext.rb:
115:in `recursive_dependencies': undefined method `full_name' for
#<Gem::Dependency:0xb7700384> (NoMethodError)
from /srv/http/wotr.topfans.com/production/tasks/merb.thor/gem_ext.rb:
111:in `map'
from /srv/http/wotr.topfans.com/production/tasks/merb.thor/gem_ext.rb:
111:in `recursive_dependencies'
from /srv/http/wotr.topfans.com/production/tasks/merb.thor/ops.rb:
33:in `full_list'
from /srv/http/wotr.topfans.com/production/tasks/merb.thor/ops.rb:
26:in `map'
from /srv/http/wotr.topfans.com/production/tasks/merb.thor/ops.rb:
26:in `full_list'
from /srv/http/wotr.topfans.com/production/tasks/merb.thor/main.thor:
130:in `install'
from /srv/http/wotr.topfans.com/production/gems/gems/thor-0.9.9/lib/
thor/task.rb:27:in `send'
from /srv/http/wotr.topfans.com/production/gems/gems/thor-0.9.9/lib/
thor/task.rb:27:in `run'
from /srv/http/wotr.topfans.com/production/gems/gems/thor-0.9.9/lib/
thor/task.rb:20:in `parse'
from /srv/http/wotr.topfans.com/production/gems/gems/thor-0.9.9/lib/
thor/runner.rb:155:in `method_missing'
from /srv/http/wotr.topfans.com/production/gems/gems/thor-0.9.9/lib/
thor/task.rb:27:in `send'
from /srv/http/wotr.topfans.com/production/gems/gems/thor-0.9.9/lib/
thor/task.rb:27:in `run'
from /srv/http/wotr.topfans.com/production/gems/gems/thor-0.9.9/lib/
thor/task.rb:20:in `parse'
from /srv/http/wotr.topfans.com/production/gems/gems/thor-0.9.9/lib/
thor.rb:78:in `start'
from /srv/http/wotr.topfans.com/production/gems/gems/thor-0.9.9/bin/
thor:7
from bin/thor:31:in `load'
from bin/thor:31
On Dec 18, 12:57 pm, Star Trader <[email protected]> wrote:
> Would this address the issue of bundling Slices as well?
>
> On Dec 18, 8:24 am, "Yehuda Katz" <[email protected]> wrote:
>
> > That is, in fact, the current approach. I would consider allowing you to
> > specify an additional directory to search for non-public gems. Would that
> > help?
> > -- Yehuda
>
> > On Thu, Dec 18, 2008 at 1:40 AM, Jacques Crocker <[email protected]> wrote:
>
> > > I currently have several non public gems in my project installed using
> > > the 1.0.6 thor task. Here's how I bundled them:
>
> > > - install the gems from .gem file to my system gems
> > > - add to dependencies.rb
> > > - run thor merb:gem:install
>
> > > The thor task checks system gems first so it'll install it from there.
>
> > > From then on, it'll be in the cache, so after you check it in, it'll
> > > be available via redeploy for others.
>
> > > Probably not an ideal scenario so I think the bug is still valid. But
> > > this technique should serve as a workaround.
>
> > > On Dec 18, 1:34 am, Carl Lerche <[email protected]> wrote:
> > > > I believe that non public gems are a known issue. I just added a
> > > > ticket in lighthouse to be sure.
>
> > > >http://merb.lighthouseapp.com/projects/7433/tickets/1139-should-be-ab...
>
> > > > -carl
>
> > > > On Dec 18, 1:21 am, Geoff Smith <[email protected]> wrote:
>
> > > > > Great work!
>
> > > > > Do you have any advice on how to bundle non-public gems using this
> > > > > setup?
>
> > > > > On Dec 17, 8:26 pm, Wayne Seguin <[email protected]> wrote:
>
> > > > > >http://www.jingproject.com/
>
> > > > > > On Dec 17, 2008, at 15:23 , Carl Lerche wrote:
>
> > > > > > > Hey guys,
>
> > > > > > > I recorded a screencast last night with Yehuda demonstrating the
> > > new
> > > > > > > features in Merb 1.0.5 (aka, the new bundler release). I believe
> > > most
> > > > > > > of the pains people have been having are now solved, so check it
> > > out.
>
> > >http://splendificent.com/2008/12/merb-dependencies-and-bundler-conque...
>
> > > > > > > later,
> > > > > > > -carl
>
> > --
> > Yehuda Katz
> > Developer | Engine Yard
> > (ph) 718.877.1325
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
