[
https://issues.apache.org/jira/browse/BIGTOP-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758376#comment-13758376
]
Mark Grover commented on BIGTOP-1059:
-------------------------------------
+1 and committed!
FWIW, it looks you modified the original patch to create the new patch. That
doesn't really work because of the way git creates patches (with hashes
embedded in them for the good reason of reliability). The best way to avoid
such problems is to make a commit in your own git repo and then regenerate the
patch:-)
In any case, I modified the patch and committed. Thanks again for doing this!
> Add path option for pig.jar to pig smoke pom.xml
> ------------------------------------------------
>
> Key: BIGTOP-1059
> URL: https://issues.apache.org/jira/browse/BIGTOP-1059
> Project: Bigtop
> Issue Type: Bug
> Components: Tests
> Affects Versions: 0.6.0
> Reporter: jay vyas
> Assignee: jay vyas
> Priority: Minor
> Fix For: 0.7.0
>
> Attachments: BIGTOP-1059.1.patch, BIGTOP-1059.2.patch
>
>
> The pig.jar path is hardcoded in the existing
> test-execution/smokes/pig/pom.xml file, which means that tarball based pig
> deployments or non-standard pig install locations cannot use the smoke test.
> Also, the pom.xml in test-execution/smokes could use a couple of small
> comments since it is different than the other test-executions as of this date
> (i.e. it depends on an external smoke rather than one created in
> test-artifacts).
--
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
