--- michael sorens <[EMAIL PROTECTED]> wrote:
> Basically I was considering having a non-Task java
> class to provide more or less output if run from ant
> and if verbose is set or not. But this is not a
> high-priority issue...
>
> Also, I found the answer to (1) -- takes a
> level just as the
Basically I was considering having a non-Task java class to provide more or
less output if run from ant and if verbose is set or not. But this is not a
high-priority issue...
Also, I found the answer to (1) -- takes a level just as the listeners
you described for custom tasks, I found.
On Wed,
--- michael sorens <[EMAIL PROTECTED]> wrote:
> Thank you, Matt, for such a prompt answer to (2) and
> (4).
> Anyone else have any thoughts on (1) and (3)? Matt
> implies "can't be done"...
To elaborate further, a custom BuildLogger is not a
custom task and thus falls more under the (3) category
Thank you, Matt, for such a prompt answer to (2) and (4).
Anyone else have any thoughts on (1) and (3)? Matt implies "can't be done"...
On Wed, 26 Jan 2005 13:45:15 -0800 (PST), Matt Benson <[EMAIL PROTECTED]>
wrote:
--- michael sorens <[EMAIL PROTECTED]> wrote:
From the command line, one may use
--- michael sorens <[EMAIL PROTECTED]> wrote:
> From the command line, one may use -v to get more
> verbose output.
> How is this verbose-state accessed...
> (1) ...from within the build file (i.e. ant property
> presumably) ?
> (2) ...from within a custom task ?
> (3) ...from within a generic Ja
From the command line, one may use -v to get more verbose output.
How is this verbose-state accessed...
(1) ...from within the build file (i.e. ant property presumably) ?
(2) ...from within a custom task ?
(3) ...from within a generic Java class, if possible ?
(4) Are there guidelines for what cons
