[
https://issues.apache.org/jira/browse/PIG-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olga Natkovich updated PIG-1632:
--------------------------------
Status: Resolved (was: Patch Available)
Resolution: Fixed
> The core jar in the tarball contains the kitchen sink
> ------------------------------------------------------
>
> Key: PIG-1632
> URL: https://issues.apache.org/jira/browse/PIG-1632
> Project: Pig
> Issue Type: Bug
> Components: build
> Affects Versions: 0.8.0, 0.9.0
> Reporter: Eli Collins
> Assignee: Eli Collins
> Fix For: site, 0.9.0
>
> Attachments: pig-1632-1.patch, pig-1632-2.patch
>
>
> The core jar in the tarball contains the kitchen sink, it's not the same core
> jar built by ant jar. This is problematic since other projects that want to
> depend on the pig core jar just want pig core, but
> pig-0.8.0-SNAPSHOT-core.jar in the tarball contains a bunch of other stuff
> (hadoop, com.google, commons, etc) that may conflict with the packages also
> on a user's classpath.
> {noformat}
> pig1 (trunk)$ jar tvf build/pig-0.8.0-SNAPSHOT-core.jar |grep -v pig|wc -l
> 12
> pig1 (trunk)$ tar xvzf build/pig-0.8.0-SNAPSHOT.tar.gz
> ...
> pig1 (trunk)$ jar tvf pig-0.8.0-SNAPSHOT/pig-0.8.0-SNAPSHOT-core.jar |grep -v
> pig|wc -l
> 4819
> {noformat}
> How about restricting the core jar to just Pig classes?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
