[
https://issues.apache.org/jira/browse/BIGTOP-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13757807#comment-13757807
]
jay vyas commented on BIGTOP-1059:
----------------------------------
Are you sure this is the case for the pig tests? In any case , sure I'll
remove the comment :) .. but meanwhile, (i think) the only pig tests in bigtop
are for the pigsmokes, of which i think there is only one version published on
maven central. (if im wrong please correct me, would love to run the official
bigtop smokes for pig if there are some for pig 0.9.x or .10.x)...
jays-MacBook-Pro:bigtop-apache Jpeerindex$ git checkout
remotes/origin/branch-0.1
Previous HEAD position was c4875b2... BIGTOP-12. Add HCatalog to Bigtop
HEAD is now at cfb44ef... Excluding .gitignore files from dist for now.
jays-MacBook-Pro:bigtop-apache Jpeerindex$ find ./ -name pig
.//src/pkg/common/pig
.//src/pkg/deb/pig
.//src/pkg/rpm/pig
.//test/suites/smokes/pig
jays-MacBook-Pro:bigtop-apache Jpeerindex$ vim
.//test/suites/smokes/pig/pom.xml
jays-MacBook-Pro:bigtop-apache Jpeerindex$ cat
.//test/suites/smokes/pig/pom.xml | grep smokes
<artifactId>pigsmokes.smoke-tests</artifactId>
<name>pigsmokes</name>
> 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
> Reporter: jay vyas
> Priority: Minor
> Attachments: BIGTOP-1059.1.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
