agmcleod
agmcleod

Reputation: 13621

bundler: not executable: rake

I'm in the process of setting up JRuby 1.7 in a ubuntu vagrant box to work with torquebox. I'm using the torquebox-remote-deployer gem to deploy the archive file and the app stuff to the virtual machine. Now, when the gem tries to execute bundle exec rake db:migrate, I get the following error:

bundler: not executable: rake

Now, when i check in the vendor/bundle/jruby/1.9/bin directory, rake and all the other needed executables are there. I've also tried running the bundle command through the local jruby install to ensure it is called properly, but I get the same result

/opt/jruby/bin/jruby -S bundle exec rake db:migrate

Any suggestions? If you need more info, just ask.

Upvotes: 1

Views: 2598

Answers (3)

Manish Shrivastava
Manish Shrivastava

Reputation: 32040

If same question will be for rails script file solution will be:

Just update file permission to executable. It worked for me.

 chmod 777 -R script/filename.rb

Cheers!

Upvotes: 1

Justin Johnson
Justin Johnson

Reputation: 1

This is due to a "bug" with jar.

https://bugs.java.com/bugdatabase/view_bug?bug_id=6194856

I ended up creating a separate ruby script for fixing permissions that I invoke with torquebox:remote:exec["bundle exec jruby path/to/script"].

Upvotes: 0

James
James

Reputation: 3362

So is the rake file that's there actually marked as executable?

Not sure how you'd end up in that situation to begin with but the error message seems to be saying that 'rake' itself is there but just not marked executable (+x).

Upvotes: 5

Related Questions