With RVM, and maybe other situations, we see this kind of thing:
$ java -jar app.war -S script/rails c
Loading production environment (Rails 3.2.12)
jruby-1.7.4.dev :001 > JRUBY_VERSION
=> "1.7.3"
jruby-1.7.4.dev :002 > IRB.conf[:PROMPT_MODE]
=> :RVM
Basically, its picks up the RVM .irbrc configuration, which thinks our JRuby runtime is the RVM ruby in use. But actually we are using the JRuby inside of the WAR.
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/1446619-s-script-rails-console-is-picking-up-rvm-s-irbrc?utm_campaign=plugin&utm_content=tracker%2F136961&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F136961&utm_medium=issues&utm_source=github).
With RVM, and maybe other situations, we see this kind of thing:
Basically, its picks up the RVM .irbrc configuration, which thinks our JRuby runtime is the RVM ruby in use. But actually we are using the JRuby inside of the WAR.
--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/1446619-s-script-rails-console-is-picking-up-rvm-s-irbrc?utm_campaign=plugin&utm_content=tracker%2F136961&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F136961&utm_medium=issues&utm_source=github).