-
-
Notifications
You must be signed in to change notification settings - Fork 161
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
Improve development environment #240
Conversation
This is great. I suggest you update https://github.com/cucumber/aruba/blob/master/CONTRIBUTING.md to explain how to use the bootstrap and test scripts, then merge it in. |
Thinking about it, I'm not sure why we need |
There was a talk from a guy from github. Using |
It's more a convience thing, that other developers do not need to think about running |
OK well I don’t mind it. My fingers will always tend to run `rake` in a Ruby project in any case.
|
Rebased, added documentation and make use of the bootstrap script on travis to make sure it really works. |
Go ahead and merge it then Dennis!
|
Access Denied. |
Ok. Done. |
\o/
|
Remove ruby 1.9.3 from supported rubies
Ruby 1.9.3 is End of Life. I see no reason to officially support a ruby
version which does not get any bugfixes from core developers.
Add support for JRuby 2 and 2.1 mode
Debugging
pry
seems to be the debugger-tool in the ruby-world. Together with byebug(ruby 2 only) even code walking is possible. The stack_explorer plugin gives
you a nice access to the stack trace. The doc-plugin makes ruby doc available from within a pry session
License Finder
aruba
seems be used widely. So extra care should be taken with licensingissues. The license_finder helps
you with that. It tracks license of all uses libraries. I whitelisted the MIT
and the BSD-licenses, I think there's no problem here. I excluded the gems
which are part of the
development
-group. They are not needed for thecore-functionality.
@jarl-dk @mattwynne Feedback?