I have jruby 1.5.6 and warbler 1.2.1.
jruby -S gem list works fine so jruby command has no problems.
jruby -S warble says “jruby: No such file, directory, or command –
warble”.
What’s the problem with warbler?
On 18 January 2011 17:10, Mauro [email protected] wrote:
I have jruby 1.5.6 and warbler 1.2.1.
jruby -S gem list works fine so jruby command has no problems.
jruby -S warble says “jruby: No such file, directory, or command – warble”.
What’s the problem with warbler?
please help!
Is Warbler listed in your Gemfile?
On 18 January 2011 18:15, Jeffrey L. [email protected] wrote:
Is Warbler listed in your Gemfile?
That’s my Gemfile:
source ‘http://rubygems.org’
gem ‘rails’
if defined?(JRUBY_VERSION)
gem ‘activerecord-jdbc-adapter’
gem ‘activerecord-jdbcpostgresql-adapter’
gem ‘jdbc-postgres’
else
gem ‘postgres-ruby’, :require => ‘postgres’
end
gem “jruby-openssl”
gem “will_paginate”, “~> 3.0.pre2”
gem “rubycas-client”
gem ‘foreigner’
gem ‘warbler’
gem ‘jquery-rails’
gem ‘devise_ldap_authenticatable’
don’t you have to do :
bundle exec warble
?
calling jruby warble assumes that you’ve gem installed warbler
manually and not with bundler.
Jay
Interesting. When I had a similar issue I was able to put it in my
Gemfile and run jruby -S bundle install, and the issue was resolved.
Sorry.
On 18 January 2011 19:20, Jay McGaffigan [email protected] wrote:
don’t you have to do :
bundle exec warble
?
calling jruby warble assumes that you’ve gem installed warbler
manually and not with bundler.
If I call simply warble it says command not found.
I’ve found a strange thing: if I run bundle install it installs
warbler but jruby -S warble don’t run.
Then I uninstall the gem and reinstall it via jruby -S gem install
warbler.
Now jruby -S warble works.
Why?
Also, in your Gemfile, you can use :platforms to define gems to include
for specific platforms, ie:
platforms :jruby do
gem “json-jruby”, “= 1.4.1”
gem “jruby-openssl”, “= 0.7"1”
end
platforms :ruby_18 do
gem “json”, “= 1.4.2”
end
That might help
when you install gems through bundler … it is my understanding that
it doesn’t always install them in your jruby installation directory.
jruby -S
tells jruby to execute the script in the jruby/bin directory named
a bundle install does not put warbler there. (at least on my mac)
It puts the gems it installs into it’s own directory.
To execute a gem’s binary (in this case the warble command) you have
to do jruby -S bundle exec warble
Jay
On 18 January 2011 20:28, Jay McGaffigan [email protected] wrote:
when you install gems through bundler … it is my understanding that
it doesn’t always install them in your jruby installation directory.
Installed with bundler I have all my gems under
jruby-1.5.6/lib/ruby/gems/1.8/gems.
Also warbler it seems to be installed under that directory.
bundle show warbler:
jruby-1.5.6/lib/ruby/gems/1.8/gems/warbler-1.2.1.
If I uninstall it and reinstall via jruby -S gem install warbler, then
jruby -S warble works.
It is very strange.
Does bundle exec warbler work when warbler is installed via bundler?
It is probably because bundler doesn’t put gem executables in your path
(or jruby’s bin directory).
On 19 January 2011 11:21, Nick G. [email protected] wrote:
Does
bundle exec warblerwork when warbler is installed via bundler?It is probably because bundler doesn’t put gem executables in your path
(or jruby’s bin directory).
bundle exec warble woks.
So I’ve to always use bundle exec for warbler?
Hi Mauro,
Maybe not the easiest solution, but I used to get these sorts of errors
frequently with bundler until I started using rvm.
http://rvm.beginrescueend.com/rvm/install/
It takes a few minutes to get set up and understand, but once you are
going, a lot of the pain goes away. I’d wager that installing it will
fix your problem.
On 19 January 2011 18:29, Nick G. [email protected] wrote:
So I’ve to always use bundle exec for warbler?
I guess if it works, but I’d have thought that if you’ve installed the
right version of warbler using jgem, then it should be executable via
jruby -S. Doing a bundle install shouldn’t be removing that gem, in
fact bundler should just use that version if it matches. There is no
need for you to remove the gem installed version of warbler just because
you’re using bundler.
I’ve installed warbler using bundle install.
Warbler gem version is 1.2.1.
As I said if I uninstall it and reinstall via jruby -S gem install
warbler, it works without using bundle exec.
So I’ve to always use bundle exec for warbler?
I guess if it works, but I’d have thought that if you’ve installed the
right version of warbler using jgem, then it should be executable via
jruby -S. Doing a bundle install shouldn’t be removing that gem, in
fact bundler should just use that version if it matches. There is no
need for you to remove the gem installed version of warbler just because
you’re using bundler.
What version of bundler do you have installed?
PS If you’ve got five minutes to spare, give rvm a go. It has stopped
my hair from falling out. I just gave your gemfile a go from a fresh
environment and it all just worked. It really helps managing all those
PATH and Gem environment so you don’t have to mess about with jruby -S.
By the way, I’ve got nothing to do with that project 
I just love it.
On Wed, 2011-01-19 at 16:19 +0100, Mauro wrote:
On 19 January 2011 11:21, Nick G. [email protected] wrote:
Does
bundle exec warblerwork when warbler is installed via bundler?It is probably because bundler doesn’t put gem executables in your path
(or jruby’s bin directory).bundle exec warble woks.
I’ve installed warbler using bundle install.
Warbler gem version is 1.2.1.
As I said if I uninstall it and reinstall via jruby -S gem install
warbler, it works without using bundle exec.
Have you filed a JIRA issue for this? I am having the same problem:
Gem binaries for gems installed with Bundler are missing. Installing
the same gem with jruby -S gem install works fine.
–
With kind regards
Uwe K.
Kubosch Consulting
[email protected]
On 23 January 2011 10:07, Uwe K. [email protected] wrote:
I’ve installed warbler using bundle install.
Warbler gem version is 1.2.1.
As I said if I uninstall it and reinstall via jruby -S gem install
warbler, it works without using bundle exec.Have you filed a JIRA issue for this?
No, I don’t know how.
On 23 January 2011 11:21, Uwe K. [email protected] wrote:
This should allow you to log in
- After login select the JRuby project
- Select Issues => Create Issue from the top menu just below the Codehaus logo.
Tell me if you have any trouble. I have heard the captcha is hard
Yes it is hard, I’ve tried 10 times without success, it is very boring.
Here is how
- Go to http://jruby.org/
- Click “GET INVOLVED”
- Click “Issue Tracker”
This should take you to
http://jira.codehaus.org/browse/JRUBY - Click the small “Log In” link in the top right corner.
- Click the TINY “Sign up” link just below the Username text field
- Fill in the form and click “Sign up”
This should allow you to log in - After login select the JRuby project
- Select Issues => Create Issue from the top menu just below the
Codehaus logo.
Tell me if you have any trouble. I have heard the captcha is hard
On 2011-01-23, at 10:46, Mauro wrote:
To unsubscribe from this list, please visit:
–
With kind regards
Uwe K.
Kubosch Consulting
[email protected]
WOOHOO!
Next time will be easier.
On 2011-01-23, at 11:49, Mauro wrote:
- Click the TINY “Sign up” link just below the Username text field
To unsubscribe from this list, please visit:
–
With kind regards
Uwe K.
Kubosch Consulting
[email protected]