[
https://issues.apache.org/jira/browse/BIGTOP-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14284053#comment-14284053
]
David Capwell commented on BIGTOP-1608:
---------------------------------------
{{but at the very least : lets not wrap maven into gradle. that won't solve
anything other than just making two levels of java indirection for something
that really could just be done in a shell script.}}
I agree, gradle calling maven makes no sense. My point was to do something
like the following
{code}
$ ls -1 bigtop-tests
itest
smoke
regression
build.gradle
gradle
gradlew
{code}
So I can then do the following
{code}
./gradlew :smoke:test -Dsmoke.tests=mapreduce
./gradlew :regression:test
{code}
This would solve the itest problem since you are now in one build system, so
for mapreduce, its build.gradle says
{code}
dependencies {
compile project(':itest')
}
{code}
Gradle will only compile whats needed, so this will be just as fast as using
source, if not faster since you no longer require to recompile itest on every
run.
> 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)
