This is related to the changes involved with refactoring DailyProjectFileMetric to DailyProjectJavaFileMetric.
When I performed my tests and built Hackystat locally, I did it with the following modules: hackyBuild hackyKernel hackyReport hackyStatistics hackyStdExt hackyTelemetry The JUnit failure involves the hackyCourse module, which I did not incorporate into the build. However, there may be other modules using the DailyProjectFileMetric class that need to be updated. Is there a superset of modules I can test to ensure my build replicates the nightly build? The only downside to this approach is that to perform a "freshStart junitAll" on all these modules is very time consuming and a burden to productivity when performing incremental changes. Thanks, Mike ----- Original Message ----- From: [EMAIL PROTECTED] Date: Tuesday, November 9, 2004 3:52 am Subject: [HACKYSTAT-DEV-L:260] Hackystat-ALL Build Failed > Hackystat build (configuration Hackystat-ALL) failed. > Build report is available at > http://xenia.ics.hawaii.edu/hackyDevSite/configurationBuildReport.do?year=2004&month=11&day=9&configuration=Hackystat-ALL > Build Time Stamp: Tue Nov 09 03:52:25 HST 2004 > >
