[
https://issues.apache.org/jira/browse/PIG-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12913738#action_12913738
]
Eli Collins commented on PIG-1632:
----------------------------------
Hey Olga,
Thanks for the feedback. Agree that we want the out of box experience to use
the same versions of other jars we've been testing with, but shouldn't that
happen by bundling the necessary jars in eg the lib directory rather than
embedding all the jars inside the core pig jar?
If people want all the dependencies bundled into a single jar, how about I
update the patch so the release has two jars: a pig.jar which is like the
current one (has all the other jars bundled in) and a pig-core.jar which just
has pig?
Thanks,
Eli
> 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
> Fix For: site, 0.9.0
>
> Attachments: pig-1632-1.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.
