Austen has informed me that the command package was left out from the review and that it should be reviewed as it plays a key role in our new MVC structure. The review has already been updated in eclipse and updating hackyInstaller2 will download the updated .jupiter file.

Greetings, folks:

This coming Wednesday (08.10.2005) at 12:30pm in POST 307, we will be reviewing the new MVC structure in the hackyInstaller2 module. To perform this review:

0. Install and/or update (a) the Eclipse Jupiter plug-in and (b) The Hackystat Jupiter sensor. 1. Update the hackyInstaller2 module from CVS. ***Please note that the module is hackyInstaller2!
2. Select "Post-MVC Refactoring" as the ReviewID.

Please review the following files:
The following files are located in the src folder:
Control Package:
* Control.java
* Request.java

Control.command Package:
* Command.java
* HelpCommand.java
* InstallOrUpdateSensorCommand.java
* SetHostAndKeyCommand.java
* SetPropertyCommand.java
* UninstallSensorCommand.java

Model Package:
* Model.java
* ModelEvent.java
* ModelListener.java

View (CLI) Package:
* Cli.java

The following files can be found in the sensors/src folder:
* EclipseSensorInstaller
* BuildSensorInstaller

We don't have any specific questions this time. We are just interested in your opinions and code suggestions. If you want you may also look at one of the sensor xml files (located in the same package with its respective installer java file).

-------------------------------------------------------------
Supplemental Links and Resources:

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!


Sorry for the mistake,
Team InstaHack!

Reply via email to