[
https://issues.apache.org/jira/browse/PIG-1334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12899593#action_12899593
]
Scott Carey commented on PIG-1334:
----------------------------------
Sure, pig-<version>-core.jar can be deployed to address this. deploying
pig-<version>.jar with packaged dependencies in addition to -core OK but
non-standard practice. A -sources and -javadoc is trivial to add and very high
value (My IDE will automatically link source and javadoc, for example).
Maven/Ivy has "optional" dependencies, where a consumer must opt-in to pulling
them but a direct build of pig will pull them. There is also 'included' scope
which has a slightly different meaning with similar effect.
Other things like JUnit are clearly test scope and should not be in any
published jar.
I am coming at this from the POV of a developer that wants to have Pig as a
dependency for writing LoadFuncs and UDFs. For that, I only need the pig
classes which should be available without baggage via a quick Ivy/Maven
dependency declaration.
> Make pig artifacts available through maven
> ------------------------------------------
>
> Key: PIG-1334
> URL: https://issues.apache.org/jira/browse/PIG-1334
> Project: Pig
> Issue Type: Improvement
> Reporter: Olga Natkovich
> Assignee: niraj rai
> Fix For: 0.8.0
>
> Attachments: mvn-pig.patch, mvn_pig_2.patch, mvn_pig_3.patch,
> mvn_pig_4.patch
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
