What we really need is your dependency module to _tell us_ what the dependencies are.
Would that be hard?
Yes. It would be hard in some cases because... Maybe I didn't explain it all that well but I'll try again.
hackyAnt requires hackyPerf. Not because it needs hackyPerf to compile or to run tests correctly. This means that hackyAnt does not use any code from hackyPerf directly. hackyAnt contains sensors for the Perf SensorDataType, however these Ant Sensors only use SensorShell not the SensorDataType. So you can see that hackyAnt doesn't require hackyPerf to compile. However, if a Hackystat Administrator builds hackyAnt it gives the impression that if someone uses the Perf Sensor that when it is sent to the server it will be stored. That isn't true if hackyPerf isn't built because there would be no Perf SensorDataType.
If a Hackystat administrator builds hackyKernel, hackyReport, hackyStatistics, hackyStdExt, and hackyAnt. Everything will compile and pass all tests. Everything will appear fine except for one printed message I showed in an earlier email. However, the Hackystat server will not store Perf data because the SDT won't be defined.
To conclude. hackyAnt implicitly requires hackyPerf. Currently, the only way to ensure that module dependencies are correct for hackyAnt is to rely on developers.
thanks, aaron
ps.. if you think this is confusing think about the poor soul who is trying to build hackyAnt.
