[
https://issues.apache.org/jira/browse/BIGTOP-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14283525#comment-14283525
]
David Capwell commented on BIGTOP-1608:
---------------------------------------
Having a hard time getting this to be at the top level gradle; not sure how to
merge source sets between projects. Is there a reason that itest is managed
outside of this gradle? Life will be easier if you just have one groovy and
everything is a sub-project from there.
The simplest way to implement this would be to have {{bigtop-tests}} that has
one root gradle project. Here itests would live, and so would smoke. Under
smoke you would have the same setup, but they are just sub projects, so
':smoke-tests:mapreduce' vs ':mapreduce'.
thoughts?
> 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
> Reporter: David Capwell
> Assignee: David Capwell
> 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)
