You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Doug Cutting (JIRA)" <ji...@apache.org> on 2010/02/25 01:58:27 UTC
[jira] Resolved: (AVRO-426) Releases should include a rubygem
[ https://issues.apache.org/jira/browse/AVRO-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Doug Cutting resolved AVRO-426.
-------------------------------
Resolution: Fixed
Hadoop Flags: [Reviewed]
I just committed this.
Next time, a single patch file that can be applied with 'patch -p 0' would be appreciated.
I changed it to put the gem into dist/ruby, and to first make that directory.
It prints a few warnings when it runs, but I assume those should be ignored?
> Releases should include a rubygem
> ---------------------------------
>
> Key: AVRO-426
> URL: https://issues.apache.org/jira/browse/AVRO-426
> Project: Avro
> Issue Type: Improvement
> Components: ruby
> Reporter: Ryan King
> Assignee: Ryan King
> Priority: Minor
> Fix For: 1.3.1
>
> Attachments: v1-0001-AVRO-426-Rake-task-to-build-a-rubygem-and-move-it-to-t.txt, v1-0001-AVRO-426-Run-the-rake-task.txt, v1-0002-AVRO-426-Run-the-rake-task.txt
>
>
> From cutting on the mailing list:
> "We just need a patch that causes the top-level './build.sh dist' to create this in the top-level dist/ directory."
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.