'ParseTree =2.0.1'
Reported by Matthew King | January 30th, 2008 @ 05:37 PM
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]
Comments and changes to this ticket
-
Chris Wanstrath January 30th, 2008 @ 07:13 PM
- → State changed from “new” to “open”
Can you verify that ParseTree 2.1.1 works with Ambition? If so I'll bump the version.
-
Matthew King January 31st, 2008 @ 06:33 AM
I can verify that it absolutely does NOT work. Suck. Will see what's changed in ParseTree.
-
Matthew King January 31st, 2008 @ 09:32 AM
Or actually, I can verify that I am suffering from gem dependency hell.
-
Matthew King January 31st, 2008 @ 10:06 AM
Okay, so with ParseTree 2.1.1, all specs pass. ActiveRecord 2.0.2 or Ruby2Ruby 1.1.8 will break Ambition.
-
Matthew King January 31st, 2008 @ 10:08 AM
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.
-
ronin-13570 (at lighthouseapp) February 15th, 2008 @ 02:54 AM
I can confirm that it doesn't break ambition itself but it may well break the specs.
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Tim Kofol