I've just committed updates to the hackySensor_Jupiter module, and I think my branch is ready for review. I will confer with Hongbing and send an announcement tomorrow.
If you want to look at the current state, do an SVN switch to: svn://hackydev.ics.hawaii.edu/hackystat/branches/HACK-631 I basically needed to change the sensor to send pMap data, and update the docbook to document the "optional" properties that are being sent on the pMap. After SVN switching, you can see the revised docbook by doing an 'ant hackyCore_Build.buildDocBook'. So, the process in a nutshell: (1) Create a branch of hackystat named with your <jira-ID>. Do a freshStart all.junit to sanity check. (2) Evolve the hackySdt_* module, updating tests and so forth. (3) Update higher level (hackyApp_*) modules that use this SDT. Most often, your evolution will change the wrapper class API, so it will be easy to find these by simply recompiling the entire system. (4) Update the lower level (hackySensor_*) modules that use this SDT. You have to figure out how to send the right data in the right way. Use a module like hackySensor_Locc, which has already been evolved to use FileMetric with pMaps, as your guide. (5) Update the docbook to indicate the new required and optional properties. Often, you won't know what the optional properties are until you've looked at lower-level modules. (6) Of course, another freshStart all.junit would be a Good Thing at this point. (7) Commit changes to your branch (8) Schedule the code review of your branch. Cheers, Philip
