[ https://issues.apache.org/jira/browse/BIGTOP-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14120133#comment-14120133 ]
Konstantin Boudnik commented on BIGTOP-1372: -------------------------------------------- bq. make hadoop-rpm $MVN_OPTION="test" I actually don't like the idea of making build overly flexible. If one can pass arguments into {{do-component-build}} script it has a potential of affecting the content of produced build. Most obvious use case would be - having all dependencies prefetched and locally installed in .m2 - passing in {{-o}} parameter to maven to prevent updates - resulting build might potentially has wrong deps built in Besides, it isn't a task of packaging part of the build to test anything. The assumption is that our source artifacts are already tested during their own release cycle. Bigtop community doesn't necessary have an expertise to test releases of all the components we bundle into the stack. > 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 hbase" will run > tests for the artifacts: hadoop and hbase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)