3.1 and rvm, not talking to each other?

I have come to the conclusion that 3.0.1 was much better than 3.1 when it comes to rvm, ruby upgrade through rvm, various gemsets etc.

At this point, I am considering that I should just continue to use 3.0.1 and upgrade to a newer version that fixes 3.1 woes. I find it extremely annoying to open a simple project in RM 3.1 when I have a more-or-less straightforward Gemfile.
First off, it (the ruby interpreter add/remove SDK dialog) just does not consult rvm. The same project opens fine with 3.0.1. The moment I use 3.1, everything is bad.
I also find attaching the Gems separately rather annoying when I have a Gemfile.

Anyone else in the same boat?

-Kedar

11 comments
Comment actions Permalink

Same boat.  RubyMine 3.0.1 handled RVM and Gemfiles much better.  I don't know if the issue in 3.1 is with RVM, Bundler, or both.  But for whatever reason RubyMine 3.1 now doesn't believe I have the necessary gems available.  3.0.1 worked just fine.

0
Comment actions Permalink

Good. At least I am not alone. Can RM team make some comment on these and other 3.1 problems with rvm gemset handling?

-Kedar

0
Comment actions Permalink

First off, it (the ruby interpreter add/remove SDK dialog) just does not consult rvm. The same project opens fine with 3.0.1. The moment I use 3.1, everything is bad.

RubyMine 3.1 and 3.0 store caches/settings/etc in different folders. So 3.0 version may use ruby SDK which were generated early. Which rvm version do you use, is it global or local rvm installation?

I also find attaching the Gems separately rather annoying when I have a Gemfile.

Explain please what do you mean and difference between new and old RubyMine behaviours.

0
Comment actions Permalink

I'm using RVM 1.1.6, with my gemsets and rubies installed globally under /usr/local.  I did make sure to choose the correct Ruby/Gemset combination, though it did seem that RubyMine correctly referred to what the project .rvmrc file specified.  So it appeared to correctly find the .rvmrc file, but didn't recognize the gems installed in the specified RVM gemset.

Regarding the gem "attach" logic, I didn't notice anything differently from 3.0.1.  In 3.0.1 I still had to manually attach the gems to the project.  It's just that with 3.1 RubyMine couldn't find any gems to attach.

0
Comment actions Permalink

I'm using RVM 1.1.6, with my gemsets and rubies installed globally under /usr/local.

I've reproduce it. This is a regression in 3.1. Fix will be available in 3.1.1 bug fix update.

I can suggest a workaround for the problem:
- Quite RubyMine
- Create empty "~/.rvm" directory.
- Launch RubyMine. On startup all gemsets should be detected. Please don't delete ~/.rvm folder until 3.1.1 bug fix update.

0
Comment actions Permalink

OK, thanks Roman.  I'll probably just wait for 3.1.1.  3.0.1 works pretty well for me.

0
Comment actions Permalink

> I also find attaching the Gems separately rather annoying when I have a Gemfile.
Explain please what do you mean and difference between new and old RubyMine behaviours.

I guess I am not understanding why one has to do this separate step of "Attaching the installed gems". I mean, if Gemfile is the only way to create a "self-contained" Rails application, why does one need to bother with Attaching/Installing the Gem?
Just update the Gemfile and let RM do the rest. RM should (and I think it does) respond to changes to Gemfile and use the gems listed in it.

I feel like this "Attach Gems" is an alternate workflow which I don't quite understand.
And yes, this is same as it was in RM 3.0.1.

Am I making it clear or am I completely off?

-Kedar

0
Comment actions Permalink

Roman, is this bug fixed in the 3.1.1 EAP you guys released today?

0
Comment actions Permalink

Just tried RM 3.1.1, and it looks like this problem still exists.  That's disappointing.  Is there a defect number I should be tracking for this?

In the mean time, back to 3.0.1, I guess.

0
Comment actions Permalink

My mistake, it does appear to have been fixed in 3.1.1.  I apparently had emptied my RVM gemset.  After running "bundle install", RM correctly sees the gems that were installed in the shared location.

0

Please sign in to leave a comment.