Gem dependency

#66

Hello Matt,

Thanks for this great framework!

Recently I tried to create an app with halcyon under JRuby and found a problem running the init.

In http://github.com/mtodd/halcyon/... you defined a dependency, facets, as part of the merb-core as an asset. Wouldn't it be better defining the dependency as


%w(rubygems rack extlib facets merb-core/dispatch/router json uri).each {|dep|require dep}

In this way the halcyon init ran as expected.

Thanks,

Janos

PS. I'll investigate why the app start didn't work but that is an other story :)

Reported by yaanno · October 11th, 2008 @ 03:37 PM

Activity

Matt Todd
- Milestone changed from Release 0.6.0 to Release 0.5.5
- Tag changed from init to config, dependency, init, merb
Thanks for the ticket, Janos.

Well, facets is (or, at least, was) a part of merb-core and not just referred to as 'facets' (because there is another, different RubyGem called 'facets').

However, with the most recent development going on with merb-core, a lot of the internal dependencies of Merb are changing and the Router itself is changing drastically. I've begin implementing the updated Router (which will resolve dependency issues as well) but for now, since it is a moving target, I will just wait until it's fully released (0.9.9 or 1.0.0).

What version of Merb do you have installed?

October 11th, 2008 @ 05:50 PM
yaanno
Hi Matt,

I did not realize that the merb-core vendor facets is a different stuff than facets rubygem, sorry if I posted something misleading.

My merb gem is version 0.9.8

Good luck, can't wait your updated fw :)

Janos

October 11th, 2008 @ 06:02 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.