[jira] [Commented] (BIGTOP-2172) get rid of gradlew inside of subprojects

["Konstantin Boudnik (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BIGTOP-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15049827#comment-15049827 ] 

Konstantin Boudnik commented on BIGTOP-2172:
--------------------------------------------

Perhaps needs to be forked into a separate JIRA, but we also need to get rid of explicit reference to {{compileGroovy}} task elsewhere smoke-tests. This task will be executed automatically and there's no need to require a user to run it.

> get rid of gradlew inside of subprojects
> ----------------------------------------
>
>                 Key: BIGTOP-2172
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-2172
>             Project: Bigtop
>          Issue Type: Bug
>          Components: tests
>    Affects Versions: 1.0.0
>            Reporter: Konstantin Boudnik
>             Fix For: 1.1.0
>
>
> It seems that having a separate {{gradlew}} under {{bigtop-tests/smoke-tests}} goes against KISS principle. With it we'll have to separately support two different wrappers. Instead, we can just use the top level gradlew file, when the tests have to be executed.
> This works just fine (from the top-level)
> {code}
> ./gradlew -b bigtop-tests/smoke-tests/build.gradle clean test -Dsmoke.tests=mapreduce
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)