What about redirecting output? http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#redirectTestOutputToFile
Doesn't help? On Sat, 5 Dec 2015 03:17 Nghia Tran <[email protected]> wrote: > Sorry - by "this" I meant > https://issues.apache.org/jira/browse/TINKERPOP-1019. I can work on that > and offer a pull request. > > On Fri, Dec 4, 2015 at 9:13 AM, Nghia Tran <[email protected]> > wrote: > > > Hi, > > I'd like to take this on. > > > > Regards, > > Nghia Tran > > > > On Fri, Dec 4, 2015 at 9:10 AM, Stephen Mallette <[email protected]> > > wrote: > > > >> It was painful and I'm scarred, but the simple task for "make builds log > >> less so that travis will be happy" turned into quite an affair. In any > >> case, I believe that what I've implemented gives us complete control of > >> logging during maven builds, which makes a lot of things possible: > >> > >> 1. The "ci" profile can now work nicely with Travis and the build output > >> far more readable > >> 2. We can stop doing println type output in tests and get control over > >> what > >> gets written when: https://issues.apache.org/jira/browse/TINKERPOP-1019 > >> 3. We can easily turn on TRACE level logging, alter logging formats, etc > >> for improved ability to debug builds. > >> > >> By default I've set all log levels in all projects to WARN. For > >> spark-gremlin, there are some additional restrictions (jetty/akka/etc). > >> If > >> you want to ever modify these settings while debugging, you can do so as > >> described here: > >> > >> > >> > http://tinkerpop.incubator.apache.org/docs/3.1.1-SNAPSHOT/dev/developer/#logging > >> > > > > >
