Yup, understood and opened an issue in Bundler since it seems to be the culprit in the end: https://github.com/carlhuda/bundler/issues/issue/832
Just FYI if there's any other Windows/RSpec2/Autotest/Bundler user :) Jarmo On Nov 10, 5:23 pm, David Chelimsky <dchelim...@gmail.com> wrote: > On Nov 10, 2010, at 8:54 AM,JarmoPertmanwrote: > > > > > > > > > > > On Nov 10, 4:06 pm, David Chelimsky <dchelim...@gmail.com> wrote: > >> On Nov 10, 2010, at 7:54 AM,JarmoPertmanwrote: > > >>> I didn't get any replies about that problem so far but i just managed > >>> to find out how to make it work manually. > > >> What manual change did you make? > > >>> The problem is that the bundle exec is not working like this on > >>> Windows: > >>> bundle exec C:\bin\pik\Ruby-187-p302\bin\ruby > > >>> But works like this: > >>> bundle exec C:\bin\pik\Ruby-187-p302\bin\ruby.exe > > > Sorry that i didn't bring it out more - i replaced bin\ruby with bin > > \ruby.exe and was able to run that bundle exec from the command line > > manually. So if the path to Ruby is constructed by RSpec then it is > > bug in RSpec's otherwise it could be somewhere else. Maybe even in > > bundler, which could just add that missing ".exe" by itself... That's > > why i'm asking. > > RSpec subclasses Autotest > (https://github.com/rspec/rspec-core/blob/master/lib/autotest/rspec2.r...), > generates the command, and delegates the ruby executable to Autotest > (https://github.com/rspec/rspec-core/blob/master/lib/autotest/rspec2.r...). > So it is Autotest that is deciding what ruby command to use. > > Cheers, > David > _______________________________________________ > rspec-users mailing list > rspec-us...@rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
