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.

'ParseTree =2.0.1'

#183

Locking to a specific version of ParseTree makes Ambition unusable with Merb.

$ merb -i

...

irb(main):001:0> require 'ambition'

Gem::Exception: can't activate ParseTree (= 2.0.1), already activated ParseTree-2.1.1]

Reported by Matthew King · January 30th, 2008 @ 05:37 PM

State: open
Milestone: none
Assigned to: Chris Wanstrath Chris Wanstrath

Activity

  1. Chris Wanstrath
    Chris Wanstrath
    • State changed from new to open

    Can you verify that ParseTree 2.1.1 works with Ambition? If so I'll bump the version.

    January 30th, 2008 @ 07:13 PM

  2. Matthew King
    Matthew King

    I can verify that it absolutely does NOT work. Suck. Will see what's changed in ParseTree.

    January 31st, 2008 @ 06:33 AM

  3. Matthew King
    Matthew King

    Or actually, I can verify that I am suffering from gem dependency hell.

    January 31st, 2008 @ 09:32 AM

  4. Matthew King
    Matthew King

    Okay, so with ParseTree 2.1.1, all specs pass. ActiveRecord 2.0.2 or Ruby2Ruby 1.1.8 will break Ambition.

    January 31st, 2008 @ 10:06 AM

  5. Matthew King
    Matthew King

    Crap, sorry about the numerous small updates.

    ActiveRecord 2.0.2 appears to break (and it should) the test helper hack where we make fake MySQL and PostgreSQL connections. It should not break Ambition proper.

    January 31st, 2008 @ 10:08 AM

  6. ronin-13570 (at lighthouseapp)
    ronin-13570 (at lighthouseapp)

    I can confirm that it doesn't break ambition itself but it may well break the specs.

    February 15th, 2008 @ 02:54 AM

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.