Run HackyStat on your PC
A step by step guide to start HackyStat on your PC. A sequel to Diving into HackyStat
I hope this will help you quickly start running HackyStat on your PC. Feel free to provide
any feedback in case my explanation is wrong or ambiguous.
Pre-requisites.
- Java. It works with Java 1.5 but JAXB library needs to be installed separately.
- Why have the worry? Install java 1.6
Download HackyStat
- Go to the download page. The latest binaries would be available at http://code.google.com/p/hackystat/downloads/list
- Download both, hackystat-8.X.YYY-sensors-bin.zip hackystat-8.X.YYY-services-bin.zip
- Unzip both files to the same directory. e.g. C:\HackyStat.server
- You should get a directory structure like this
C:\Hackystat.server\hackystat-analysis-dailyprojectdata C:\Hackystat.server\hackystat-analysis-telemetry C:\Hackystat.server\hackystat-sensor-ant C:\Hackystat.server\hackystat-sensor-emacs ... C:\Hackystat.server\hackystat-sensor-example C:\Hackystat.server\hackystat-sensor-shell C:\Hackystat.server\hackystat-sensor-xmldata C:\Hackystat.server\hackystat-sensorbase-uh C:\Hackystat.server\hackystat-ui-wicket C:\Hackystat.server\hackystat-utilities
Configure server (on next page)
Jupiter Plugin for Code Review
There is a great open source Eclipse Plugin for Code review – Jupiter. The User Guide is now available in PDF Format.
Jupiter Eclipse Plugin has a very good integration with your IDE and your configuration management system. If you are not using any IDE, this is the right time to start using Eclipse.
If you are not using any configuraiton management system, please tell me how you can still work withing a team. More about usage of Jupiter would follow.
More about installation has been very well documented at wiki page with google code.
Here is a short note on how to perform a review using Jupiter.
- Initiate a review.
- Name the review.
- Select files for review (Optional)
- Select users who would participate in review (Necessary)
- A “review” file would be created/appended. (This file is in XML format)
- This file would be one per project. (Remember project. Not folder/file. One project, one such file. This may be a micro limitation for very huge mis-orgranized projects.)
- Share this file with all peer developers through configuration management systems.
- Ask peer developers to pull in changes from configuration management system.
- Now peer developers/reviewers should press the Purple Button with Jupiter symbol.
- Now three stages of review would be performed.
- Individual
Just collect the comments. Question is What is the issue? - Team
Question is who is going to address these comments?
Just make sure that in the end one person works on one file. Do not assign same set of source file to multiple developers. Else when you merge developer changes, line number mismatch is destined to happen. - Rework Phase
Now address the comments, and fix them.
- Individual
- At the end of all the three phases, you will have to push in changes to configuration management.
- It is suggested to have these three phases, as discrete as possible.
- Don’t forget the Golden sentence, “One developer, one source file to fix issues“
- Close the review (Remove un-necessary files from configuration management system).
Jupiter Users Group
I and the Jupiter user group would be very happy to address your issues comments.
http://groups.google.com/group/jupiter-users
Feature Update Site
You can directly use this update site within your eclipse to update the eclipse plugin
http://jupiter-eclipse-plugin.googlecode.com/svn/trunk/site/