socketry/nio4r

Need a new Java Release

CodingAnarchy opened this issue · 8 comments

CodingAnarchy commented

A patch was made for JRuby deregister errors in #217, but it wasn't released in a new gem version. As puma is using nio4r now, it would really help for that to be released for those of us using JRuby and Puma.

tarcieri commented

We should probably also tackle #220 before another release.

@ioquatix can you take care of these? If not I can when I have some time.

ioquatix commented

It is done.

mperham commented

Gentlemen, nio4r 2.5.1 was pushed today but no associated 2.5.1-java gem release so the gem currently fails to install on jruby.

  • 👍1
tarcieri commented

@ioquatix unfortunately every release needs a corresponding -java release, even if the JRuby backend is unchanged. RubyGems handling of platforms is weird that way.

  • 👍1
ioquatix commented

Oh my bad that’s my fault. I didn’t imagine it worked like that since 2.5.0 release was okay. Thanks for explaining it, I’ll fix it now.

ioquatix commented

Before we go and reinvent the wheel, is there any existing rake task/library that handles the MRI/JRuby release, e.g.

rake all_platforms:release

For lack of a better place to put it, I threw some notes/instructions here.

tarcieri commented

cc @headius @enebo

Know of any release automations for gems that need a ruby and java release, and also build a JRuby extension for the latter, that can do it all in one go?

enebo commented

@tarcieri I have not seen one but I wish we had a standard for this because I have to read docs whenever I want to build a gem which has java arch.