Anybody know where to find the reference for: [HACKYSTAT-DEV-L:54], [HACKYSTAT-DEV-L:62-66] ?
Aaron Akihisa Kagawa wrote:
Greetings, folks:
This Wednesday (09.22.2004) at noon in POST 307, we will be reviewing the JavaClassWorkspaceMapManager in the hackyStdExt module - org.hackystat.stdext.workspace.mava.javamap package. To perform this review:
0. Install and/or update (a) the Eclipse Jupiter plug-in and (b) The Hackystat Jupiter sensor.
1. Update the hackyStdExt module from CVS.
2. Select "JavaMap" as the ReviewID.
Please review the following files: * JavaClassWorkspaceMapManager.java * package.html
We are particularly concerned about the following:
1. Currently, one class path is mapped to many Workspaces. Is this the best possible design? Or should one class path is mapped to one Workspace? Note: the problems identified in [HACKYSTAT-DEV-L:54], [HACKYSTAT-DEV-L:62-66].
------------------------------------------------------------- Supplemental Links and Resources:
JavaClassWorkspaceMapManager has the following Quality Attributes (this is an experimental section):
* Code initially created on May 7, 2003 - fairly old code
* 2 developers have contributed to the code (Philip and Hongbing). Hongbing is the "expert" (ie the developer with the most active time associated with this class) for the past year and a half.
* 196 lines of code - medium sized
* Zero unit tests, although it has 90% coverage
* 7 other classes has least one reference to JavaClassWorkspaceMapManager
* Has never been reviewed
The Hackystat Code Review Guidelines: * http://hackydev.ics.hawaii.edu/hackyDevSite/doc/Review.html
The Elements of Hacky Style: * http://hackydev.ics.hawaii.edu/hackyDevSite/doc/EHS.html
Jupiter Code Review Tool documentation: * http://csdl.ics.hawaii.edu/Tools/Jupiter/Core/doc/UsersGuide.html
Hackystat Jupiter Sensor documentation:
*<http://hackystat.ics.hawaii.edu/hackystat/controller?Page=help&Subpage=install&Sensor=Eclipse-Jupiter>
Thanks for reviewing the code!
Aaron
