Description
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).