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/10/01 21:34:35 UTC
[jira] [Commented] (BIGTOP-1477) Gradle build should print errors
[ https://issues.apache.org/jira/browse/BIGTOP-1477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14155349#comment-14155349 ]
Konstantin Boudnik commented on BIGTOP-1477:
--------------------------------------------
Yup! Wanted to open a ticket like this for a long time myself - thanks!
> Gradle build should print errors
> --------------------------------
>
> Key: BIGTOP-1477
> URL: https://issues.apache.org/jira/browse/BIGTOP-1477
> Project: Bigtop
> Issue Type: Bug
> Components: build
> Affects Versions: 0.8.0
> Reporter: jay vyas
> Fix For: 0.9.0
>
>
> When building with gradle, if something fails, it doesnt seem to clearly print out why.
> For example:
> 1) if you run {{gradle mahout-rpm}} on a system without maven installed (i agree its idiotic to do this), you just get a failure message
> 2) If you do the same with the "make" command, you get a clear failure (mvn not found).
> So lets get gradle error messages as robust as possible to smooth the transition to gradle (which im in favor of)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)