views:

37

answers:

1

help rails 3 came out yesterday, we have a fully functional rails 2.3.8 app, but our deployment on heroku doesn't work because declarative_authorization demands rails 2.1 or higher

That is a very big problem, how can I solve it, any quick hacks, workarounds?

+1  A: 

Make sure your .gems file starts with:

rails --version=2.3.8

But as you've stated, declarative_authorization will then go an install the Rails 3.0.0 gems over the top of your rails install, breaking the lot. You can get around this in your gems manifest, by using:

declarative_authorization --ignore-dependencies

Of course, you'll also need to separately include each dependency for declarative_authorization in your gems manifest.

theTRON
thanks, but this does not work. We have specified rails --version=2.3.8 in .gems (and it gets loaded) the problem is, that declarative_authorization has this line s.add_dependency('rails', '>= 2.1.0')you can see it herehttp://github.com/stffn/declarative_authorization/blob/master/declarative_authorization.gemspecwhat can we do? :(
tabaluga
I ran a quick test app and had the same problem - but i've updated my answer above with a solution.
theTRON
thankyou, thankyou, thankyou :)
tabaluga