I have a very well spec'd large merb app, but unfortunately I can't test RC2 because of merb. After finding snusnu's fork of merb 1.1 (http://sick.snusnu.info/2009/06/03/migrating-to-datamapper-0100/) I thought I saw a light at the end of the tunnel, but the latest version of thor was pulled into my stack while I was updating all my gems. The latest version of thor is fubar until "Carl get's back and He and Yehuda can merge the new bundler into 1.1".
Does anybody have an idea of when merb will be datamapper 0.10.0 friendly? On Thu, Sep 10, 2009 at 4:11 AM, George<[email protected]> wrote: > > Ah I see, Ok thanks Dan. I'll look into that. > > On Sep 10, 7:10 am, "Dan Kubb (dkubb)" <[email protected]> wrote: >> George, >> >> > On windows xp it looks like we need a ".ruby_inline/ >> > Inline_RawParseTree_ab80.so" file. It's the only file listed in my >> > merb output that's not present in the folders. >> >> Are you sure that is DataMapper requiring that? I noticed the stack >> trace looks like the problem occurred when merb-action-args is being >> used, which I know relies on ParseTree and rubyinline. >> >> I can't think of anything in dm-core or dm-more that requires >> ParseTree. >> >> -- >> >> Dan >> (dkubb) > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DataMapper" 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/datamapper?hl=en -~----------~----~----~----~------~----~------~--~---
