[
https://issues.apache.org/jira/browse/PIG-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027769#comment-13027769
]
Alan Gates commented on PIG-2019:
---------------------------------
When I run ant smoketests-jar now, the resulting smoketests.jar contains:
{code}
META-INF/
META-INF/MANIFEST.MF
org/
org/apache/
org/apache/pig/
org/apache/pig/test/
org/apache/pig/test/pigunit/
org/apache/pig/test/pigunit/pig/
org/apache/pig/test/pigunit/TestPigTest.class
org/apache/pig/test/pigunit/pig/TestGruntParser$1.class
org/apache/pig/test/pigunit/pig/TestGruntParser.class
test/
test/data/
test/data/pigunit/
test/data/pigunit/top_queries.pig
test/data/pigunit/top_queries_expected_top_3.txt
test/data/pigunit/top_queries_input_data.txt
test/data/pigunit/top_queries_params.txt
{code}
Does that look correct? That seems a little thin. Smoketest just runs the
PigUnit tests?
> smoketest-jar target has to depend on pigunit-jar to guarantee inclusion of
> test classes
> ----------------------------------------------------------------------------------------
>
> Key: PIG-2019
> URL: https://issues.apache.org/jira/browse/PIG-2019
> Project: Pig
> Issue Type: Bug
> Components: build
> Affects Versions: 0.9.0
> Reporter: Konstantin Boudnik
> Assignee: Konstantin Boudnik
> Fix For: 0.9.0
>
> Attachments: PIG-2019.patch
>
>
> pigsmoke artifact uses classes from pigunit for real cluster testing.
> However, in the deployment phase the artifact comes out without the classes
> added. It happens because of the execution order of targets during deployment.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
