On 8/16/11 2:46 AM, Andrew Lee Rubinger wrote:
On 08/16/2011 12:54 AM, Jason T. Greene wrote:
> The approach might catch a missing dependency, but it will not catch an
> unnecessary dependency. It seems that only human review can get the most
> accurate results. Alternatively, it might be more correct to actually
> write real API verification tests, that does something like look for an
> expected list of packages, and erroring when an unexpected package is
> found (or a missing one).
I think about this all the time. Unfortunately, you can't catch a leaked
API unless you test for all possible leaks. If anyone's got a fine idea
how to deal with this, I'm all ears.
Sure you can, any package that shows up that is not on the list is a leak.
--
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat