[
https://issues.apache.org/jira/browse/CRUNCH-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Friedrich updated CRUNCH-76:
-------------------------------------
Attachment: CRUNCH-76-Create-binary-release.patch
First try at creating a binary release, containing license files, our
artifacts, and dependencies, based on Flume's setup. I had to rebuild the
source distribution in the process because it doesn't work from a sub-module
(the resulting archives are almost identical).
Is there anything else to include? We still have the old scrunch artifacts that
we dropped from the last release. Where do we want to go with that?
> Create binary release artifacts
> -------------------------------
>
> Key: CRUNCH-76
> URL: https://issues.apache.org/jira/browse/CRUNCH-76
> Project: Crunch
> Issue Type: Task
> Reporter: Josh Wills
> Assignee: Matthias Friedrich
> Labels: artifact
> Attachments: CRUNCH-76-Create-binary-release.patch
>
>
> Per BIGTOP-612, it would be helpful for Crunch to include compiled jars as a
> convenience as part of our release artifacts, like most of the other Hadoop
> projects. There are some pros and cons to doing this, so this JIRA is here to
> track the discussion from both the Crunch and Bigtop perspectives.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
