You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Konstantin Boudnik (JIRA)" <ji...@apache.org> on 2015/01/26 20:05:38 UTC
[jira] [Commented] (BIGTOP-1621) Migrate itest to gradle
[ https://issues.apache.org/jira/browse/BIGTOP-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292240#comment-14292240 ]
Konstantin Boudnik commented on BIGTOP-1621:
--------------------------------------------
The gradle part of the build looks ok. I think it'd be nice to have repositories defined in the top-level build, etc., but it's good start - let me play with it.
I feel somewhat uncomfortable with the surgery performed on the README file. Not everything in there is related to the failure testing. And I don't see a need to have two or more READMEs: let it be one which includes sections on the functionality and build instructions. Better yet - let's hook up the build part to the top-level gradle. Can we do that?
> 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
>
>
> 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)