Defect #10474

Gems version conflict in Redmine core and plugins

Added by John Yani almost 6 years ago. Updated over 4 years ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Plugin API
Target version:-
Resolution: Affected version:

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.

History

#1 Updated by Harry Garrood over 4 years ago

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.

#2 Updated by Toshi MARUYAMA over 4 years ago

  • Category set to Plugin API

#3 Updated by Toshi MARUYAMA over 4 years ago

  • Subject changed from Gemfile and plugins to Gems version in Gemfile conflict in Redmine core and plugins

#4 Updated by Toshi MARUYAMA over 4 years ago

  • Subject changed from Gems version in Gemfile conflict in Redmine core and plugins to Gems version conflict in Redmine core and plugins

Also available in: Atom PDF