[
https://issues.apache.org/jira/browse/AVRO-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13853714#comment-13853714
]
Ches Martin commented on AVRO-1063:
-----------------------------------
If you switch to using Bundler in build automation, I'd suggest also using
Bundler's built-in release automation Rake tasks and dropping Echoe which is
currently used -- the presence of both would probably confuse most Ruby-savvy
contributors. I would be willing to work up a patch for this (as [~martinkl]
mentioned it has become fairly standard), but it's a bigger change to review
than is most immediately necessary to fix the build.
[~cutting], I believe changing the build to run {{rake install:development &&
rake test}} should address the problem for the moment. I'm not very familiar
with the project as a whole yet, could you point me to where this build
configuration lives in source control? I'd need to find that to submit a patch
for Bundler too.
> Ruby client should use multi_json rather than being locked down to yajl
> -----------------------------------------------------------------------
>
> Key: AVRO-1063
> URL: https://issues.apache.org/jira/browse/AVRO-1063
> Project: Avro
> Issue Type: Improvement
> Components: ruby
> Reporter: Paul Dlug
> Assignee: Duke
> Priority: Minor
> Fix For: 1.7.6
>
> Attachments: AVRO-1063.diff, gemfile.patch
>
>
> The avro ruby client uses yajl for JSON serialization which is just one of
> many suitable JSON implementations for ruby. The multi_json gem provides a
> wrapper for JSON serialization selecting the fastest library available (Oj is
> now even faster than Yajl) and falling back to a pure ruby implementation
> bundled with multi_json. Requiring yajl also precludes the ruby gem from
> being used under jruby since it requires a C extension.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
