On Sun, 05 May 2002, Conor MacNeill <[EMAIL PROTECTED]>
wrote:
> Do you mean reproting the error to the dependency which introduce
> the problem? I wonder how feasible it would be and how many false
> positives it would generate.
I think you can only do it manually and after you've clearly
identified which component is responsible - Gump is already doing this
for a certain type of build failure in FOP (the second regexp):
<nag from="Sam Ruby <[EMAIL PROTECTED]>">
<regexp to="[EMAIL PROTECTED]"/>
<regexp pattern="/\[style\] .* java.lang.NullPointerException/"
to="[EMAIL PROTECTED]"/>
</nag>
Maybe we should have done that for Latka after dIon clearly identified
it as a Xerces problem, but then again the problem was fixed shortly
thereafter.
Stefan
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
