-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plugin does not work with Cucumber 2.0 #60
Comments
Can someone be specific about the issues? A backtrace would give us a place to start, but a failing automated test would be ideal. We can either make changes to Cucumber's API or help fix this plugin or both. But we need more information! 😄 |
That's all the information that I can see... I don't know how to make yardoc print a backtrace for why there was an error loading the plugin. Once I find out how to get more information, I'll try to report that here |
Let me paste that here as well. Unfortunately yard does not print backtrace of plugins that failed to load (too bad IMO). By modifying the gem I managed to get to the issue (by modifying gem to stop requiring version 1.3):
That's from And here's reply from @mattwynne from the other issue:
|
Hmm, I don't know how this is usually tested (there are no tests). However, I just commented out the offending require, updated the cucumber dependency to
Everything seemed to run just fine without the require :s I then rolled the dependency back to There don't seem to be any references to |
@pghalliday , I pushed your changes to ruby-gems as a band-aid solution for folks who want to use yard in their projects still, without building from github. |
@tk8817 cool, thanks |
Maybe this could help someone... https://cookingcode.wordpress.com/2016/10/09/how-to-install-yard-cucumber-windows/ |
The plugin can't work with a Cucumber 2.0 dependency. There are some bugs in Cucumber 1.3 that have only been fixed in 2.0 and later.
The text was updated successfully, but these errors were encountered: