gump-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Leo Simons <>
Subject Re: Nagging the cause vs. Nagging the effect
Date Thu, 05 Feb 2004 19:35:05 GMT
Stefano Mazzocchi wrote:
> I think the key is that the gump runs as for Gump or Gumpy do *not* 
> contain enough information.

what might work sometimes is (pattern) matching the <package/> 
statements of the dependencies against the errors produced by javac or 
unit tests, and cvs history.

that would've caught the xml-batik error, I think. I mean,


org.apache.batik.script.rhino.BatikSecurityController is not abstract 
and does not override abstract method 

in org.mozilla.javascript.SecurityController
     [javac] public class BatikSecurityController extends 
SecurityController {

is clearly showing to any human programmer that whatever produces the


package is the problem, since presumably 
didn't change since the previous build yet started causing a compilation 

you'd need to be pretty intelligent about parsing the error message 
though. But it seems to be there in some way, without needing /that/ 
many statistics.


- Leo Simons

Weblog              --
IoC Component Glue  --
Articles & Opinions --
"We started off trying to set up a small anarchist community, but
  people wouldn't obey the rules."
                                                         -- Alan Bennett

View raw message