[
https://issues.apache.org/jira/browse/BIGTOP-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14322303#comment-14322303
]
Konstantin Boudnik commented on BIGTOP-1621:
--------------------------------------------
This is how gradle pulls in subprojects (1st line); in the second one I declare
a module name that differs from the module's directory name.
As for review: the objective of the JIRA is covered, I think. We can take
further advancements elsewhere... What do you think?
> Migrate itest to gradle
> -----------------------
>
> Key: BIGTOP-1621
> URL: https://issues.apache.org/jira/browse/BIGTOP-1621
> Project: Bigtop
> Issue Type: Improvement
> Components: tests
> Affects Versions: 0.9.0
> Reporter: jay vyas
> Assignee: jay vyas
> Fix For: 0.9.0
>
> Attachments: BIGTOP-1621.patch, BIGTOP-1621.patch, BIGTOP-1621.patch
>
>
> build itest w gradle, so that we can call gradle tasks to install it as a
> local dependency, as part of supporting one single testing framework. See
> BIGTOP-1608.
> This is the first step, the minimal work necessary to allo gradle based smoke
> tests to use gradle best itest framework via calling {{gradle install}}
> later those doing publishing of itest jars can finalize the process and test
> gradle for publishing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
