Redmine

According to real-life statements Yehuda Katz on the most recent RUG::B meeting, even he would not recommend bundler for Rails 2.3.5 projects. It will be properly supported and recommended in Rails 3.0 (with an upgrade path via 2.3.8, see #5603), but I would strongly advise on not using bundler today for Redmine. It's a pain in the ass today.

Holger, may you please be more specific? Why do you against bundler today? Does this patch broke something for you? What the pain?

As for me this patch fixed practical problems, simplified plugins installation process and didn't broke anything.

The main issue is that Bundler + additional Rails/Redmine plugins don't play well at all, as you will be back to manual dependency resolution. Though it does indeed fix the i18n issue. Note that moving to Rails 2.3.8 would, too. I myself simply use another RVM gemset for Redmine development.

Note that RVM and Bundler interfere for some people, which was a concern raised in the Redmine IRC channel (or so I was told0. This is mainly caused by both meddling with the GEM_HOME and GEM_PATH environment variables. Although some people seem to still have issues with using both Bundler and RVM simultaneously, I did not run into any related issues since Bundler 0.9, since both projects are now written in a manner so that they are aware of each other.

Yeah, there were problems with RVM and bundler, but there are no now. RVM gemsets are more buggy (at least for me), and I definitely don't want to use RVM on production server, where I happened to have two different Rails apps. Bundler is a rescue for me.

Proposed patch loads Gemfiles from plugins, if there are any. Redmine developers may stick with specific gem version for patch releases, and upgrade gems with minor and major releases. I believe this will make plugins developers (like me) life easier.

Though in that case switching to Bundler on trunk would be an option, as the 1.0 release will probably be done earlier than Redmine's.

Konstantin Haase wrote:

Though in that case switching to Bundler on trunk would be an option, as the 1.0 release will probably be done earlier than Redmine's.

Redmine's 1.0 RC will be in two weeks. We have already stopped feature development and are fixing the last set of bugs. I think Redmine 1.1 will be released this winter and there's a good chance it will be able to support Rails 3 and Bundler.

Eric Davis wrote:

Konstantin Haase wrote:

Though in that case switching to Bundler on trunk would be an option, as the 1.0 release will probably be done earlier than Redmine's.

Redmine's 1.0 RC will be in two weeks. We have already stopped feature development and are fixing the last set of bugs. I think Redmine 1.1 will be released this winter and there's a good chance it will be able to support Rails 3 and Bundler.

Oh. Ok, my bad.

Per discussion in IRC: target version is 1.1.

'RVM gemsets are more buggy'

This should most definitely not be the case in the latest RVM. All known bugs related to gemset usage have been fixed. I have worked closely with the Bundler team to ensure that RVM gemsets and Bundler 0.9.26+ work very well together.

'I definitely don't want to use RVM on production server'

I find this statement amusing since RVM was developed for the purpose of production servers.

~Wayne

Bundler is now 1.0 and stable, and doesn't use .bundle/ directory anymore, so it might be use-able even with rails 2.3.5 I think. It would be far better than actual manual installs, rake gems:install, and hacks on i18n... Please let us know if anybody has an objection.

Patch updated (includes 'pg' as rails db adapter).

related to chili#290

I've also seen a FR talking about externalizing ruby-ldap.

I pushed my github repository branch.
https://github.com/marutosi/redmine/commits/redmine-bundler

$ git log -n1 | cat
commit 311610f795f4e134940509dcdb463bed9d3210de
Author: XXXXXXXXXX
Date:   Fri May 13 09:17:29 2011 -0700

    [#290] Only print the plugin Gemfile messages when $DEBUG is set

    --HG--
    branch : redmine-bundler-hg-git

I have an error message when I start my local application like below: /usr/local/lib/ruby/gems/1.9.1/gems/railties-3.0.6/lib/rails/plugin.rb:22:in `inherited': You cannot inherit from Rails::Plugin (RuntimeError). It looks like this message is related to the engine. I asked RubyML about this, it says "there might be a risk that the primary function of 'plugin' which properly works in 2.3 would not be operational in 3.0 engine. In short, I believe the regression occurs in 3.0 in this part. Thus, it is a trend to wait until 3.1 which has the perfect engine function is released". How do you treat this engine? Do you wait until 3.1 release? I do not know how to compile, so need to have your advise on this.

I give up to install on Mingw Ruby 1.8.6.

$ ruby --version
ruby 1.8.6 (2010-02-04 patchlevel 398) [i386-mingw32]

$ bundle install
Fetching source index for http://rubygems.org/
Fetching source index for http://rubygems.org/
Fetching source index for http://rubygems.org/
Installing rake (0.9.2)
Using activesupport (2.3.11)
Installing rack (1.1.2)
Using actionpack (2.3.11)
Using actionmailer (2.3.11)
Using activerecord (2.3.11)
Using activeresource (2.3.11)
Using bundler (1.0.15)
Installing coderay (0.9.8)
Using edavis10-object_daddy (0.4.3)
Installing hoe (2.10.0) r:/Ruby186/lib/ruby/site_ruby/1.8/rubygems/installer.rb:
170:in `install': hoe requires RubyGems version >= 1.4. Try 'gem update --system' to update RubyGems itself. (Gem::InstallError)
        from r:/Ruby186/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/source.rb:101:in `install'
        from r:/Ruby186/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/rubygems_integration.rb:78:in `preserve_paths'
        from r:/Ruby186/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/source.rb:91:in `install'
        from r:/Ruby186/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/installer.rb:58:in `run'
        from r:/Ruby186/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/rubygems_integration.rb:93:in `with_build_args'
        from r:/Ruby186/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/installer.rb:57:in `run'
        from r:/Ruby186/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/spec_set.rb:12:in `each'
        from r:/Ruby186/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/spec_set.rb:12:in `each'
         ... 7 levels...
        from r:/Ruby186/lib/ruby/gems/1.8/gems/bundler-1.0.15/lib/bundler/vendor/thor/base.rb:389:in `start'
        from r:/Ruby186/lib/ruby/gems/1.8/gems/bundler-1.0.15/bin/bundle:13
        from r:/Ruby186/bin/bundle:19:in `load'
        from r:/Ruby186/bin/bundle:19

$ gem update --system
Updating RubyGems
Updating rubygems-update
ERROR:  Error installing rubygems-update:
        rubygems-update requires Ruby version >= 1.8.7.
ERROR:  While executing gem ... (NoMethodError)
    undefined method `version' for nil:NilClass

Related link:
https://www.chiliproject.org/projects/chiliproject/wiki/Bundler

Do you plan to merge these changes to your github rails-3.1 branch ?

Etienne Massip wrote:

Do you plan to merge these changes to your github rails-3.1 branch ?

Rails-3.1 branch has already these revisions excluding csv.
Renaming view files (.rhtml to .html.erb) is too hard to merge.
But, I will merge later.

Jean-Philippe Lang wrote:

Random failures (including the one you mention) occur with ruby-1.8.7-p358 and mysql.

Fixed in r8909.

I have troubles after this issue and opened a theme in the Help forum: http://www.redmine.org/boards/2/topics/29070. I need help so as to proceed with Redmine.