invalid option: --profile when running with Bundler (cucumber for ruby)

[bunnymatic]

I just recently started running into an issue with the Rake tasks. It seems that the options that I'm trying to pass to cucumber are getting skipped and passed to the ruby as another command (or something) which leads to:

.rbenv/versions/2.3.0/bin/ruby -S bundle exec cucumber --profile default
Using the default profile...
0 scenarios
0 steps
0m0.000s

invalid option: --profile

For this test run, I've added --name nomatch so it actually doesn't try to run any scenarios (just to highlight the issue).

I dug into the source a bit and it seems like in here:

https://github.com/cucumber/cucumber-ruby/blob/master/lib/cucumber/rake/task.rb#L81

where the cmd is built, in the use bundler path, it builds a shell command like

.rbenv/versions/2.3.0/bin/ruby -S bundle exec cucumber --profile default

and (at least on my mac) the --profile argument appears to apply to the ruby command (not cucumber). I'm not sure where the quoting should go and will try to take a closer look. But if there is a known solution/workaround here, please let me know. I'm on cucumber (2.3.2)

Thanks

[bunnymatic]

Whoops. I actually was on 2.1.0 and after bumping to 2.3.2 the problem went away.
I pre-emptively pulled that 2.3.2 from the Gemfile.lock not remembering that I'd just updated gems.

Closing the issue. Sorry to bother you.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.