[
https://issues.apache.org/jira/browse/BIGTOP-1477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14163532#comment-14163532
]
Konstantin Boudnik commented on BIGTOP-1477:
--------------------------------------------
Here's make output for the same case as above
{noformat}
dpkg-buildpackage: host architecture amd64
fakeroot debian/rules clean
dh clean
dh_testdir
dh_auto_clean
ant clean
Can't exec "ant": No such file or directory at
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 215.
dh_auto_clean: ant clean failed to to execute: No such file or directory
make: *** [clean] Error 2
dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2
debuild: fatal error at line 1350:
dpkg-buildpackage -rfakeroot -D -us -uc -b failed
make: *** [/biggy/workspaces/bigtop/build/bigtop-tomcat//.deb] Error 29
{noformat}
I am not arguing against the improvement - I am just not sure how to pursue it.
> 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)
