As a follow-up to the last email, I am using the list of modules in the build.xml of hackyBuild to ensure that the changes to DailyProjectFileMetric succeed for the entire system.
I've found that the changes to this class have trickled upstream into modules such as hackyQuality and hackyCourse, as well as hackyTelemetry. What is more interesting to me is the process that other people follow when making changes that will affect several modules in Hackystat. Here is the (simple) approach I am now following. I'd really like to hear what others are doing. Maybe we can form a universal methodology based on what everyone says. 1) Checkout or update all modules listed in build.xml of hackyBuild 2) Perform modifications to code. In this case I refactored the DailyProjectFileMetric class into DailyProjectJavaFileMetric and moved it to a new package (using Eclipse refactoring). 3) Build Hackystat locally using "ant -q freshStart" in hackyBuild. 4) Run "ant junitAll" in hackyBuild (3+4 can be combined in 1 step) 5) Commit modified code to CVS. Any suggestions for improvement or personal insights about your approach? 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 > >
