[
https://issues.apache.org/jira/browse/BUILDR-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12911106#action_12911106
]
Alex Boisvert commented on BUILDR-510:
--------------------------------------
New documentation:
h3. Verbosity and Tracing
By default, Buildr is moderately verbose, meaning that it attempts to give you
enough context into what's happening during the build.
It's possible to silence Buildr if you're inconvenienced by its default
verbosity by issuing,
{% highlight sh %}
$ buildr --silent
{% endhighlight %}
On the other hand, if you want Buildr to give you more context in order to
trace what's happening, you can use the @-t@ options:
{% highlight sh %}
$ buildr -t
{% endhighlight %}
Using @-t@ will also display backtraces if and when they occur.
Many components can be individually configured to display more output if you're
debugging a specific area of your build. For instance, you could use
@--trace=javac,groovyc@ to enable tracing of the Java and Groovy compilers:
{% highlight sh %}
$ buildr --trace=javac,groovyc
{% endhighlight %}
If you don't know which tracing category you need to enable or if you want a
full firehose worth of traces, you can enable all traces:
{% highlight sh %}
$ buildr --trace=all
{% endhighlight %}
> Add support for trace categories: --trace=foo,bar
> --------------------------------------------------
>
> Key: BUILDR-510
> URL: https://issues.apache.org/jira/browse/BUILDR-510
> Project: Buildr
> Issue Type: Improvement
> Reporter: Alex Boisvert
>
> As proposed and discussed on the mailing list,
> http://buildr.markmail.org/thread/tcm3coxxflwb7xgj
> e.g.
> buildr --trace # traces everything
> buildr --trace=tasks # traces just build-related bits -- task executions,
> things logged with `trace` in buildr & extensions
> buildr --trace=ant,javac # ups the verbosity for just ant and javac
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
