[
https://issues.apache.org/jira/browse/BIGTOP-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14059537#comment-14059537
]
Konstantin Boudnik commented on BIGTOP-1372:
--------------------------------------------
On top of what [~Virginia Wang] just said.
To clear up something from the legacy standpoint: the
'installAllLocalArtifacts' is an awful hack that I've done to get us going. If
you look into how the packages.gradle is done you'll see a much more elegant
build system that allows you do to 'all' or one or a few named packages build.
I think it is only fair to have a somewhat similar functionality for test
artifacts and test execution. I am also pretty sure - after implementing the
packages build - that components discovery and tasks generation can be done
dynamically, further reducing the need for maintenance.
> Bigtop needs feature that takes in multiple arguments to build specific
> components at command line
> --------------------------------------------------------------------------------------------------
>
> Key: BIGTOP-1372
> URL: https://issues.apache.org/jira/browse/BIGTOP-1372
> Project: Bigtop
> Issue Type: Improvement
> Components: Build
> Affects Versions: 0.7.0
> Reporter: Dawson Choong
> Fix For: 0.8.0
>
>
> Bigtop needs feature that takes in multiple arguments to build specific
> components at command line. For instance, "$ gradle hadoop cnode hbase" will
> run tests for the artifacts: hadoop, cnode, and hbase. Either build.gradle
> must be modified to achieve this or a second file that will be included in
> build.gradle
--
This message was sent by Atlassian JIRA
(v6.2#6252)
