You can pass the -t
/ --trace
flag to Buildr to trace execution, e.g.,
% buildr -t debug package
The trace flag support several (undocumented) categories to narrow down the amount of tracing to specific topics; here are some of the current ones:
-t java # runs java in -verbose mode
-t javac # runs javac in -verbose mode
...
If you want the entire list of topics, you can grep the source code:
$ find lib -name "*.rb" | xargs grep -E "trace\?"
lib/buildr/scala/doc.rb: cmd_args << '-verbose' if trace?(:scaladoc)
lib/buildr/scala/doc.rb: cmd_args = [ '-d', target, (trace?(:vscaladoc) ? '-verbose' : ''),
lib/buildr/scala/compiler.rb: cmd_args << "-debug" if trace?(:scalac)
lib/buildr/scala/compiler.rb: args << "-verbose" if trace?(:scalac)
lib/buildr/java/doc.rb: cmd_args = [ '-d', target, trace?(:javadoc) ? '-verbose' : '-quiet' ]
lib/buildr/java/ecj.rb: args << '-verbose' if trace?(:ecj)
lib/buildr/java/compiler.rb: args << '-verbose' if trace? :javac
lib/buildr/java/compiler.rb: cmd_args = [ trace?(:apt) ? '-verbose' : '-nowarn' ]
lib/buildr/java/external.rb: args << '-verbose' if trace?(:javac)
lib/buildr/java/ant.rb: options.merge!(:logger=> Logger.new(STDOUT), :loglevel=> Logger::DEBUG) if trace?(:ant)
lib/buildr/java/ant.rb: setMessageOutputLevel((trace?(:ant) && 4) || (verbose && 2) || 0)
lib/buildr/java/emma.rb: ant.emma :verbosity=>(trace?(:emma) ? 'verbose' : 'warning') do
lib/buildr/java/commands.rb: options[:verbose] ||= trace?(:java)
lib/buildr/java/commands.rb: cmd_args = [ trace?(:apt) ? '-verbose' : '-nowarn' ]
lib/buildr/java/commands.rb: cmd_args = [ '-d', options[:output], trace?(:javadoc) ? '-verbose' : '-quiet' ]
lib/buildr/groovy/doc.rb: cmd_args = [ '-d', target, trace?(:groovydoc) ? '-verbose' : nil ].compact
lib/buildr/groovy/compiler.rb: options[:verbose] ||= trace?(:groovyc) if options[:verbose].nil?
lib/buildr/core/application.rb:def trace?(*category)
lib/buildr/core/test.rb: error ex.backtrace.join("\n") if trace?