Closed drscream closed 7 years ago
Thanks for taking the time to figure this out. Once you are confident, let me know and I'll merge/publish a version.
From my point of view it's stable we've the plugin running in production since ~14 days now. But anyway I assume the above part should be fixed
Do you have an expected release date?
@louisnayegon, I could provide you with a build I made but it would be no official build from @rosskevin :-)
@drscream I'll wait
I don't have much time to put into this, so if you will take it to the finish line I will publish.
I will create some dev and test setup tomorrow (or maybe this evening). I hope I could get everything finished by the end of this week.
@drscream, is it possible you could package an unofficial .jar
containing these changes (and make it available on your fork) until this is fully tested and resolved?
@rosskevin I would recommend we should merge and create a new release now. I would say everything looks fine from my side - if we find any issue in that release (because more people will test it) we could fix it anyway!
@unRARed if you like to test feel free to download the .jar
from: https://github.com/drscream/bamboozled-ruby-plugin/releases/tag/5.10.4
@drscream I will try it out this evening, thanks!
Confirmed working using .jar
from https://github.com/drscream/bamboozled-ruby-plugin/releases/tag/5.10.4. Was able to create a successful build with rvm
installed as root user under Ubuntu server 14.04.
If anyone is interested in maintaining/ownership, please see #25
First of all I'm sure I'm not the best Java developer and this is only a workaround based on the short check of the API documentation. Because of the error reported in #23 I tried my best to get everything working.
For that reason I've updated the build environment also to
5.14.1
. At the moment I'm testing the setup on my environment.