Defect #10474
closed
Gems version conflict in Redmine core and plugins
Added by John Yani over 12 years ago.
Updated over 1 year ago.
Description
Currently Redmine's Gemfile includes plugin Gemfiles.
This could be a problem if plugin's Gemfile contains a different version of gem.
See an example of a potential problem: https://github.com/backlogs/redmine_backlogs/issues/465
If Gemfile contain two gems, you'll get an error:
You cannot specify the same gem twice with different version requirements.
This is by design. Redmine's Gemfile includes plugin Gemfiles because it's much better to ensure that there are no unsatisfiable requirements at load time, than to not check and hope it will work. (The latter leads to hours wasted trying to debug the problems which arise)
You cannot specify the same gem twice with different version requirements.
If this happens to you, you need to edit the plugin's Gemfile to relax the version constraint. Note that you don't need to have a version requirement; you can put just gem 'foo' to tell Bundler that you don't care what version you're using.
This issue should probably be closed.
- Category set to Plugin API
- Subject changed from Gemfile and plugins to Gems version in Gemfile conflict in Redmine core and plugins
- Subject changed from Gems version in Gemfile conflict in Redmine core and plugins to Gems version conflict in Redmine core and plugins
- Status changed from New to Closed
- Resolution set to Wont fix
In a Ruby on Rails application, it is impossible to use two different versions of the same gem simultaneously.
Also available in: Atom
PDF
Updated by 
Updated by Toshi MARUYAMA 
Updated by