beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chad Schoettger <>
Subject [PATCH] BEEHIVE-1010 AptControlInterface does not detect errors from a custom control checker
Date Thu, 17 Nov 2005 21:50:41 GMT
I just posted a patch for BEEHIVE-1010.

Basically the bug was that the AptControlInterface has no way of knowing if
a custom control checker detected any errors. In order to resolve this issue
it was necessary to modify the ControlChecker interface's check() method to
return a boolean value instead of void. The boolean return value is used to
let the AptControlInterface know if there were any errors found by the
checker (denoted by a return value of false).

The ControlChecker interface is a public interface which custom checkers
must extend. Since the fix for this issue involves changing a public API I
would like to get input from the dev list from anyone who might be concerned
about this change or have any ideas for other options to resolve this issue.

- Thanks,

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message