IIRC Conor originally created the depend task.
Rob
Matt Benson wrote:
--- Conor MacNeill <[EMAIL PROTECTED]>
wrote:
Yep. Let's just do it. I'm the original offender.
Original offender?
-Matt
-
To unsubscribe, e-mail: [EMAIL PROTEC
--- Conor MacNeill <[EMAIL PROTECTED]>
wrote:
> Yep. Let's just do it. I'm the original offender.
Original offender?
-Matt
__
Do you Yahoo!?
Yahoo! Search - Find what youre looking for faster
http://search.yahoo.com
--
On Tue, 2 Mar 2004 03:45:48 -0800 (PST), Matt Benson
<[EMAIL PROTECTED]> wrote:
If we're going to change the loglevel I don't think
it's really necessary to wait for a major release. I
was only pointing out the potential for an issue. I
may tend to play devil's advocate at times and argue a
cas
--- Jose Alberto Fernandez <[EMAIL PROTECTED]>
wrote:
> However, I may be willing to accept, grudgingly,
> that this be change
> in ANT 1.7 only and not backported to ANT 1.6.x.
> So we treat this as a new feature of the task on the
> new mayor release.
> If someone has an obscure usage of this or
> From: Matt Benson [mailto:[EMAIL PROTECTED]
>
> --- Jose Alberto Fernandez <[EMAIL PROTECTED]>
> wrote:
> > OK, why would a change in an output message would
> > break
> > anyones build. We do change things when spellings
> > are incorrect.
[snip...]
> > Maybe I am wrong, but I would like to se
Here we go then: the patch simply logs at DEBUG level rather than INFO
if nothing has been acheived.
Thanks,
Rob
Antoine Lévy-Lambert wrote:
Rob Oxspring wrote:
One of my (very few) pet hates with ant is that the depends task
displays something when it performs a no-op. This seems counter to
o
Rob Oxspring wrote:
One of my (very few) pet hates with ant is that the depends task
displays something when it performs a no-op. This seems counter to
other tasks (copy, javac, zip IIRC) and means that my complex build ends
up spitting out a lot of output while doing very little. The output
On Mon, 1 Mar 2004, Jose Alberto Fernandez <[EMAIL PROTECTED]>
wrote:
> I would suggest just logging this message as debug when changes = 0.
+1
> Maybe I am wrong, but I would like to see a meaningful example.
People could be parsing log outputs, maybe with custom build
listeners, you can never
Rob Oxspring wrote:
One of my (very few) pet hates with ant is that the depends task
displays something when it performs a no-op. This seems counter to
other tasks (copy, javac, zip IIRC) and means that my complex build
ends up spitting out a lot of output while doing very little. The
output
--- Jose Alberto Fernandez <[EMAIL PROTECTED]>
wrote:
> > From: Matt Benson [mailto:[EMAIL PROTECTED]
> > Since the current behavior does not really qualify
> as
> > a bug, it is not safe to assume that a change to
> the
> > default behavior of a task would not break
> someone's
> > build.
>
>
> From: Matt Benson [mailto:[EMAIL PROTECTED]
>
> --- Rob Oxspring <[EMAIL PROTECTED]> wrote:
> > One of my (very few) pet hates with ant is that the
> > depends task
> > displays something when it performs a no-op. This
> >
> > I was wondering if there was any point in preparing
> > a patch to
--- Rob Oxspring <[EMAIL PROTECTED]> wrote:
> One of my (very few) pet hates with ant is that the
> depends task
> displays something when it performs a no-op. This
>
> I was wondering if there was any point in preparing
> a patch to not
> output/log if 0 files have been deleted. The patch
> /
One of my (very few) pet hates with ant is that the depends task
displays something when it performs a no-op. This seems counter to
other tasks (copy, javac, zip IIRC) and means that my complex build ends
up spitting out a lot of output while doing very little. The output
itself doesn't exact
13 matches
Mail list logo
