I think your next step should be the DailyProjectIssue class. I believe this class currently doesn't work. I'm not sure if we ever got it working and I think we made a bogus Unit Test. Anyway, dive into that code. One issue that I think would be a problem is that the workspaces that are sent along with the Issue Sensor Data does not have a workspace root, therefore, I believe the Issue data cannot be associated with a specific project. The solution that I was thinking about is; on the server side append a fake workspace root to all Issues. For example, if the workspace is "hackyKernel/src/org/hackystat/admin" change the internal representation to "c:/issue/hackyKernel/src/org/hackystat/admin". Then in the project definition we can add "c:/issue/" to the project's workspace root configuraiton. Another solution, and on second thought I think it is better to make the JIRA sensor append a workspace root before sending the data to the Hackystat server. (Anyway this is just a guess, and you'll have to investigate its validity).
thanks, aaron
At 09:04 PM 12/6/2004 -1000, Burt Leung wrote:
Hello Philip,
hackyIssue is now created and passes all Junit test as well as manual testing by means of sending Issue data from Jira.
I made the mistake of committing it (since the plan was to wait until after the next release). However I made sure to thoroughly test everything and it works perfectly as before.
Changes: - Documentation in hackyJira, hackyIssue has been updated. - The build.xml and build.utils.xml in hackyBuild is now updated. - The Issue SDT and analyses files that were in hackyJira have been deleted from that module and moved to hackyIssue.
Burt
