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 2014/11/13 03:00:18 UTC

[jira] [Commented] (BIGTOP-1523) Gradle install for test artifacts uses wrong sequence of the targets

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

Konstantin Boudnik commented on BIGTOP-1523:
--------------------------------------------

Tasks can not invoke each other from within: you have to use order control features like {[dependsOn}}, {{mustRunAfter}} etc to achieve the same

> Gradle install for test artifacts uses wrong sequence of the targets
> --------------------------------------------------------------------
>
>                 Key: BIGTOP-1523
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1523
>             Project: Bigtop
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 0.8.0
>            Reporter: Konstantin Boudnik
>            Assignee: Konstantin Boudnik
>             Fix For: 0.9.0
>
>
> The current sequence of components install during test artifacts build-up is
> {code}
>       installTopLevel
>       installCommon
>       installConf
>       installiTest
> {code}
> which draws an iTest artifact from a repository server, instead of build a one from the current code. {{installiTest}} should be invoked before {{installCommon}} and {{installConf}}



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