java - Disable printing of stracktrace/ BuildException output in STS Gradle -
at present running gradle 2.x/3.x builds via eclipse neo , sts gradle plugin. if there problem while building, e.g. in compilejava task detailed information of wrong (imo printed stderr in console tab of eclipse , kind of stacktrace build exception occured (imo printed stdoutin console tab).
here example output:
[sts] ----------------------------------------------------- [sts] starting gradle build following tasks: [sts] compilejava [sts] ----------------------------------------------------- [...] 1 error failure: build failed exception. * went wrong: execution failed task ':compilejava'. > compilation failed; see compiler error output details. * try: run --stacktrace option stack trace. run --info or --debug option more log output. [sts] build failed org.gradle.tooling.buildexception: not execute build using gradle distribution 'https://services.gradle.org/distributions/gradle-2.14-bin.zip'. @ org.gradle.tooling.internal.consumer.resulthandleradapter.onfailure(resulthandleradapter.java:57) @ org.gradle.tooling.internal.consumer.async.defaultasyncconsumeractionexecutor$1$1.run(defaultasyncconsumeractionexecutor.java:57) @ org.gradle.internal.concurrent.defaultexecutorfactory$stoppableexecutorimpl$1.run(defaultexecutorfactory.java:64) @ java.util.concurrent.threadpoolexecutor.runworker(unknown source) @ java.util.concurrent.threadpoolexecutor$worker.run(unknown source) @ java.lang.thread.run(unknown source) @ org.[...]
the stacktrace comes along [sts] think not directly gradle. there way suppress printing of stacktrace?
the gradle sts build plugin not provide way disable stack trace printing.
can verified looking @ how stack trace printing implemented in plugin source.
output sent same printstream, there no logging framework or configuration options allow granular control of printed.
worth noting plugin has been deprecated (and being minimally maintained) in favour of buildship plugin.
buildship plugin not exhibit same stack trace printing behaviour.
Comments
Post a Comment