[
https://issues.apache.org/jira/browse/BIGTOP-1477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14182373#comment-14182373
]
jay vyas commented on BIGTOP-1477:
----------------------------------
in fedora, i get a lovely error message with make :)
{noformat}
/..../bigtop-jayunit100/build/mahout//rpm//SOURCES/do-component-build: line 21:
mvn: command not found
error: Bad exit status from /var/tmp/rpm-tmp.USgAtf (%build)
{noformat}
I wonder why {{do-component-build}} errors arent going to standard error
directly in debian/gradle ?
> 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: backlog
>
>
> 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)
