Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

Resolving gem dependencies on frozen gems

#126

I had this problem when freezing a gem that had a dependency to a gem that I did not have on my system. The application, that was working on another machine (the one that actually did the freezing of the gem), did not work on mine.

It took me a while to realize that the gem that was frozen in the __resources directory depended on a gem that I had not installed on my system.

When freezing a gem into the resources directory of a production (jruby -S limelight freeze) the command should resolve the dependencies that the frozen gem has and freeze these into the resources directory as well.

This would avoid the 'it works on my machine' effect when shipping a production and remove one or another head ache when trying to figure out what is going on ;)

Cheers :)

Reported by Enrique Comba Riepenhausen · June 8th, 2009 @ 03:53 PM

State: new
Milestone: Future
Assigned to: nobody

Activity

  1. Micah Martin
    Micah Martin
    • Milestone changed from Limelight 0.2 to Future

    June 26th, 2009 @ 01:52 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.