[
https://issues.apache.org/jira/browse/PIG-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12896653#action_12896653
]
Scott Carey commented on PIG-1540:
----------------------------------
Here are some common use cases for pig's jar files:
Build and test pig as a developer, stand-alone: pig.jar
Use pig for pig development and debugging: pig.jar
Run pig scripts in production, trimmed down dependencies: pig-withouthadoop.jar
* Perhaps this should be trimmed down somewhat, with just pig, piggybank, and
other 'basics' that would commonly need to be used when running a pig script.
Include pig in a project (for example, a custom LoadFunc project): ????
* Here is where a maven-compatible jar, javadoc-jar, and source-jar would be
a blessing. PIG-1334 should address the javadoc and source jars as well.
> clean up pig dependencies included in jar files
> -----------------------------------------------
>
> Key: PIG-1540
> URL: https://issues.apache.org/jira/browse/PIG-1540
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.7.0
> Reporter: Scott Carey
>
> Pig's output jars are difficult to include in other projects and bloated.
> Building some jar targets for common use cases would be a big benefit to
> those consuming pig. As a bonus, if these were ready for use in a Maven
> repository, then a follow-on ticket to enable maven would be trivial.
> More information in comments to follow.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
