You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@buildr.apache.org by Harish Krishnaswamy <ha...@gmail.com> on 2008/04/16 00:36:16 UTC
Buildr::Java.java verbosity
I created a task in my project to run my app and had some issues with the
classpath, so I turned the verbosity on via verbose=true. But it made no
difference, it only shows the name of the class I am trying to run. I had to
turn the trace on to see the classpath. What is the purpose of the verbose
parameter? Shouldn't we show the complete command when its turned on?
Re: Buildr::Java.java verbosity
Posted by Harish Krishnaswamy <ha...@gmail.com>.
I guess I was trying to say "verbose=true" is not verbose enough :) Thanks!
On Tue, Apr 15, 2008 at 9:31 PM, Assaf Arkin <ar...@intalio.com> wrote:
> On Tue, Apr 15, 2008 at 3:36 PM, Harish Krishnaswamy <
> harishkswamy@gmail.com>
> wrote:
>
> > I created a task in my project to run my app and had some issues with
> the
> > classpath, so I turned the verbosity on via verbose=true. But it made no
> > difference, it only shows the name of the class I am trying to run. I
> had
> > to
> > turn the trace on to see the classpath. What is the purpose of the
> verbose
> > parameter? Shouldn't we show the complete command when its turned on?
> >
>
> Verbose is on by default.
>
> There's an option to run Buildr with less output, called --quiet, that
> turns
> verbose off. With verbose you get a lot more messages on progress, some
> tasks tell you when they're about to execute, progress bar when
> downloading
> files, etc. Quiet is much more silent (although it doesn't seem to affect
> JUnit that much).
>
> Assaf
>
Re: Buildr::Java.java verbosity
Posted by Assaf Arkin <ar...@intalio.com>.
On Tue, Apr 15, 2008 at 3:36 PM, Harish Krishnaswamy <ha...@gmail.com>
wrote:
> I created a task in my project to run my app and had some issues with the
> classpath, so I turned the verbosity on via verbose=true. But it made no
> difference, it only shows the name of the class I am trying to run. I had
> to
> turn the trace on to see the classpath. What is the purpose of the verbose
> parameter? Shouldn't we show the complete command when its turned on?
>
Verbose is on by default.
There's an option to run Buildr with less output, called --quiet, that turns
verbose off. With verbose you get a lot more messages on progress, some
tasks tell you when they're about to execute, progress bar when downloading
files, etc. Quiet is much more silent (although it doesn't seem to affect
JUnit that much).
Assaf