You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
jruby-jms repo has been archived by the owner, which means we can not submit patches or report issues upstream (technically issues can be submitted but won't get fixed).
I'm tempted to go for option 1 (vendoring) with a caveat: we should merge the JMS input and output into the logstash-integration-jms. This way we don't have to vendor the code into two repositories and duplicate any work we do to this library.
jruby-jms repo has been archived by the owner, which means we can not submit patches or report issues upstream (technically issues can be submitted but won't get fixed).
there's
Fixnum
/Bignum
warnings at the library level that are annoying and should be dealt with:reidmorrison/jruby-jms@master...kares:patch-1
there's a few options forward:
first option might be the easiest to take for the foreseeable future ...
The text was updated successfully, but these errors were encountered: