ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 13681] add a "verbose" parameter to "dependset"
Date Wed, 06 Aug 2008 17:19:21 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=13681


Jeff Holt <jeff.holt@method-r.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|enhancement                 |normal




--- Comment #2 from Jeff Holt <jeff.holt@method-r.com>  2008-08-06 10:19:20 PST ---
Such debugging information are valuable in other contexts too.

I found a bug in 1.7.0 where a target wasn't getting apply'd because the
dependset's was incorrectly identifying the "newest source".

So, here I argue two points:

First, the so-called Severity is not enhancement because it's debug code, not
feature code. Debug code is buggy when: (1) it causes abnormal termination or
(2) it fails to tell you what to do to fix your code. So, based upon this
definition of buggy debug code, I would set the severity at least no less than
"normal."

Second, even if you leave the Severity as "enhancement" you can still meet an
earlier Target Milestone if you simply enumerate the list of files are when you
render the "newest source" and the "oldest target file". Something like this:

FileResource "somefile" is the newest source of {"filea" [mtime], "fileb"
[mtime],...}

Who cares if the list is long? The point of the debug information is to
provide, well, information! How can you know what to do if you don't know upon
what the decision was made?


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

Mime
View raw message