Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Rails 3 bundler #8

Open
sudara opened this issue Jul 27, 2010 · 4 comments
Open

Rails 3 bundler #8

sudara opened this issue Jul 27, 2010 · 4 comments
Labels

Comments

@sudara
Copy link

sudara commented Jul 27, 2010

If there's an earlier version of active record in system gems, it seems that this gets required by reportable, causing this error:

sudara@ramen:/data/app/current$ bundle exec rails c
No compatible versions could be found for required dependencies:
  Conflict on: "activerecord":
  * activerecord (2.3.4) activated by reportable (>= 0, runtime)
  * activerecord (= 3.0.0.beta4, runtime) required by rails (>= 0, runtime)
  All possible versions of origin requirements conflict.

My temporary solution is to require the libs explicitly for rails:

gem 'activerecord',  '3.0.0.beta4', :require => 'active_record'
gem 'activesupport', '3.0.0.beta4', :require => 'active_support'
gem 'actionpack',    '3.0.0.beta4', :require => 'action_pack'

This is an issue with bundler 0.9.x and rails 3 beta4 - but strangely, only in production. Still need to test with bundler 1.0.x - perhaps it's a bundle issue that's been fixed.

Still, if rails is being required by reportable's Gemfile, is there a reason the other libs have to be required here too?

Thanks for the cool gem :) I built a barchart helper for raphaël, let me know if you guys would be interested in it.

@marcoow
Copy link
Contributor

marcoow commented Jul 28, 2010

I cannot reproduce this. Can you provide some more information? Also take a look at the sample Rails 3 project (http://github.com/saulabs/reportable-sample).

We would definitely be interested in a barchart helper! Can you please just fork the project and send us a pull request?

@sudara
Copy link
Author

sudara commented Jul 28, 2010

Interesting, what bundler version are you using? I'm on 0.9.26 and strangely, the issue is only in production (maybe related to how classes are loaded).

Hopefully bundler 1.x will make the problem go away. And in any case, it's not a big deal!

@marcoow
Copy link
Contributor

marcoow commented Jul 28, 2010

I'm on 0.9.26 as well. What does your Gemfile look like?

@kommen
Copy link
Member

kommen commented Feb 15, 2012

Is this still an issue with the latest reportable version?

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants