[
https://issues.apache.org/jira/browse/CRUNCH-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466652#comment-13466652
]
Matthias Friedrich commented on CRUNCH-76:
------------------------------------------
You're right, we don't really need to ship them. The problem is that one job of
crunch-test is to act as a collection of dependencies for other modules, that's
why Mockito and Hamcrest are on the "compile" scope. We could duplicate
dependencies of JUnit, Hamcrest, and Mockito in all modules that need them (on
the "test" scope"),then they would disappear from the distribution. I think
"mvn dependencies:analyze" wants us to do that, BTW.
Just adding an exclusion in the assembly descriptor would be looking for
trouble. If we'd ever use them in crunch-test, we'd probably forget to remove
the exclusion.
> 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,
> CRUNCH-76-Create-binary-release-v2.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
