On 24/10/2012, at 2:32 AM, Luke Daley wrote: > @Adam: any idea on what's going on here? > > Is Travis wrong to advertise this as the TERM?
Maybe. Or our terminal detection is broken. @Rob, can you add some trace to your build script to see if java.io.Console is available, to see if Java thinks the process is attached to a terminal? You might also try using a recent nightly build, as we made some changes to the terminal detection. > > On 01/10/2012, at 10:51 AM, Rob Fletcher wrote: > >> It reports $TERM as just `xterm` >> >> -- >> Rob Fletcher >> >> On Sunday, 30 September 2012 at 11:05, Luke Daley wrote: >> >>> >>> On 22/09/2012, at 8:21 AM, Rob Fletcher wrote: >>> >>>> Hi >>>> >>>> Is there a way to tell Gradle to generate plain console output? >>> >>> There's currently not. >>> >>>> I'm running a build on Travis CI and due to the limitations of Travis's >>>> logging it's very hard to see the wood for the trees. For example: >>>> http://travis-ci.org/#!/robfletcher/betamax/builds/2527439 I have a couple >>>> of failing tests there but it's pretty hard to pick them out from all the >>>> noise generated by the download & test running updates. >>> >>> Can you add some trace to your build to report on what the value of the >>> TERM env var is please. > > -- > Luke Daley > Principal Engineer, Gradleware > http://gradleware.com > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
