-
Notifications
You must be signed in to change notification settings - Fork 103
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
Gem version 0.1.8 doesn't work with Ruby 1.8.7 #28
Comments
Wow, what a method to be tripped up by! My inclination is to just alter the gemspec to require 1.9.3 (or 1.9.1?). With the release of Ruby 2.0, I'm not sure it makes sense to maintain backward compatibility with 1.8.7. I think I'd have to do quite a bit of testing before I was confident that, even with some modifications, the current gem would be 1.8.7 compatible, since I haven't run against 1.8.7 in probably 6 months or so. |
Support for 1.8.7 will be end-of-lifed in all R7 products w/ Ruby support in June 2013. This is when the Ruby team will cease official support of the Ruby 1.8.7 line. http://www.ruby-lang.org/en/news/2011/10/06/plans-for-1-8-7/Trevor Rosen Email: trevor_rosen@rapid7.com From: mdaines-r7 <notifications@github.commailto:notifications@github.com> Wow, what a method to be tripped up by! My inclination is to just alter the gemspec to require 1.9.3 (or 1.9.1?). With the release of Ruby 2.0, I'm not sure it makes sense to maintain backward compatibility with 1.8.7. I think I'd have to do quite a bit of testing before I was confident that, even with some modifications, the current gem would be 1.8.7 compatible, since I haven't run against 1.8.7 in probably 6 months or so. — |
OK, I'll dig into what it will take to return to 1.8.7 compliance. I'm currently confused, since I see the max_by method in the 1.8.7 documentation. I'll try to go through it in the next day or so and release a 0.1.9 that is 1.8.7 compliant. |
Turns out the problem was in wrapping on chained collection methods. 1.9 allows them to be on separate lines, but 1.8.7 requires that they are all on a single line. In any case, I've pushed 0.1.9, which should return us to 1.8.7 compatibility. |
Hi there, unfortunately it seems Nexpose Gem has a syntax that doesn't work with Ruby 1.8.7.
Using Ruby 1.9.3 with the same Gemset, the code works
The text was updated successfully, but these errors were encountered: