Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Dependency on "multi_json ~>1.3" collides with activesupport (3.1.10) #247

Closed
h5b opened this issue Jan 31, 2013 · 5 comments · Fixed by #248
Closed

Dependency on "multi_json ~>1.3" collides with activesupport (3.1.10) #247

h5b opened this issue Jan 31, 2013 · 5 comments · Fixed by #248

Comments

@h5b
Copy link

h5b commented Jan 31, 2013

Hi,

we are trying to upgrade brakeman to 1.9.1 on Rails 3.1
which has the following dependencies regarding "multi_json":

activesupport (3.1.10)
  multi_json (>= 1.0, < 1.3)

While brakeman depends on multi_json (~> 1.3) as stated in brakeman.gemspec.

require './lib/brakeman/version'

Gem::Specification.new do |s|
  [..]
  s.add_dependency "sass", "~>3.0"
  s.add_dependency "multi_json", "~>1.3"
end

The initial switch from "json_pure" to "multi_json" didn't refer to a specific
version. Could we by any chance fix this mutually exclusive dependency?

@presidentbeef
Copy link
Owner

Hi,

Thanks for reporting this! Yes, it should be possible to resolve this issue. I will look into it.

@h5b
Copy link
Author

h5b commented Jan 31, 2013

Thanks for looking into this.

@presidentbeef
Copy link
Owner

Looks like Rails 3.1 depends on MultiJson < 1.3 for the same reason Brakeman depends on MultiJson ~> 1.3: the MultiJson API started to change at that version.

However, we definitely want to avoid conflicts and support including Brakeman in Gemfiles for Rails 3.0 and 3.1, so I've moved the requirement back to ~> 1.2. I hope this allows enough overlap to fix the dependency.

If you can, please try the changes in #248 and let me know if it works for you.

@h5b
Copy link
Author

h5b commented Feb 1, 2013

Diff as found in #248 fixes the Issue. Upgrade works now and the report has been generated.
Thanks a lot!

@presidentbeef
Copy link
Owner

Great! Thanks for verifying.

Repository owner locked and limited conversation to collaborators Feb 16, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants