[
https://issues.apache.org/jira/browse/BIGTOP-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14284238#comment-14284238
]
jay vyas commented on BIGTOP-1608:
----------------------------------
1) im an agreement also w/ davids idea. if you are suggesting that gradle
transparently compiles itest into a jar , thats good.
2) Can someone here *please* tell me, what the advantage of compiling the pig
smoke test, which is just a groovy file, into a jar file is before running it
? it takes longer, and is less easy to modify. im totally against making
jars for ecosystem tests. it totally alienates the entire non-java community.
*i've never once run a suite of tests on the hadoop ecosystem that i didnt want
to modify or play with something*.
Am i crazy ? Or is there some huge benefit to hiding shell commands inside a
jar that im missing?
> all smoke-tests should compile and use iTest as source, no jar. Remove ITEST
> env variable.
> -------------------------------------------------------------------------------------------
>
> Key: BIGTOP-1608
> URL: https://issues.apache.org/jira/browse/BIGTOP-1608
> Project: Bigtop
> Issue Type: Improvement
> Components: tests
> Affects Versions: 0.8.0
> Reporter: David Capwell
> Assignee: David Capwell
> Fix For: 0.9.0
>
> Attachments: BIGTOP-1608-first-part.patch, BIGTOP-1608.1.patch
>
>
> If you try to run the smoke tests without setting {{BIGTOP_HOME}} they will
> run and be unable to find tests, so nothing runs. This variable should be
> added to checkEnv to make sure its present while running
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
