Rpsec gem binary not in bin?

This is jruby 1.6.1. Installing the rspec gem doesn’t put rspec in
bin, but it is in lib/ruby/gems/1.8/bin. Never ran into this behavior
before, how can I fix this?

Chris

This is jruby 1.6.1. Installing the rspec gem doesn’t put rspec in
bin, but it is in lib/ruby/gems/1.8/bin. Never ran into this behavior
before, how can I fix this?
This happened because rspec was bundled with jruby prior to 1.6.

To fix it, run rspec with jruby -S rspec or put lib/ruby/gems/1.8/bin on
your PATH variable.
HTH

Chris


To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Douglas Campos (qmx)
[email protected]

On Mon, May 2, 2011 at 12:34 PM, Douglas Campos (qmx) [email protected]
wrote:

This is jruby 1.6.1. Installing the rspec gem doesn’t put rspec in
bin, but it is in lib/ruby/gems/1.8/bin. Never ran into this behavior
before, how can I fix this?
This happened because rspec was bundled with jruby prior to 1.6.

To fix it, run rspec with jruby -S rspec or put lib/ruby/gems/1.8/bin

That doesn’t work.

on your PATH variable.

And that’s not acceptable.

Chris

That should have said jruby -S doesn’t work…
weird, can you give more environment details? windows/linux/osx?

Chris


To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email

Douglas Campos (qmx)
[email protected]

To fix it, run rspec with jruby -S rspec or put lib/ruby/gems/1.8/bin

That doesn’t work.

That should have said jruby -S doesn’t work…

Chris

On Mon, May 2, 2011 at 12:44 PM, Douglas Campos (qmx) [email protected]
wrote:

That should have said jruby -S doesn’t work…
weird, can you give more environment details? windows/linux/osx?

Ubuntu 10.04 LTS. jruby --help say’s -S looks in bin, I assumed it
didn’t look in the gem bin directories, and that gem binaries were all
copied to bin. That’s where other gem binaries end up.

Chris

First thought is that the unbundling put in some logic that’s
preventing the rspec binary from being copied to bin. Also noticed
that the rspec binary lives in rspec-core, not rspec. Could some bad
naming assumptions be going on there? Like it first looks to see if
there is a gem binary named after the gem, and if not it doesn’t get
copied over?

Chris