--On Wednesday, November 10, 2004 5:00 PM -1000 Aaron Kagawa <[EMAIL PROTECTED]> wrote:
I propose an Ant target that prints out the module dependencies. That way we can double check them. I also think that this module dependency is something that should go into our DocBook documentation.
Unfortunately, this is error prone, since it would rely on a developer declaring the dependency.
What we really need is your dependency module to _tell us_ what the dependencies are.
Would that be hard?
Cheers, Philip
p.s. Yes, the modularity of Hackystat is degrading; it is semi-layered, and semi-stovepiped, with no obvious rhyme or reason about why to choose one over the other for new modules. I do think about this issue frequently but have not yet had the bolt of lightning hit me with the realization of which way we should go.
