Jupiter and Java planets

It all started with a discussion with few of my buddies, who are doing a great open source application for content management. End of the discussion we figured since I was external resource for their application I should do a code walk thro of their code base. Stroke of luck for me, these are some rock solid minds of JEE technologists and I get to look at their work. Honestly the tools that they were using all simple JEE API's. Some of the API’s that stuck out for me usage of Spring API's and Spring components. For content management, they were using the friendly neighbor Jackrabbit. Imagine a world without Apache :). I got access to their trunk in Google code. I started looking into the code base, I cannot believe I saw some chinks that can be removed or addressed. Now I started writing it in as comments within the body of the code. I was almost looked at 1/3 of their code base; I had various pointers that I wanted to keep them posted and ask for their opinion on a particular logic/coding style. I was careful in my comment section to separate my tracking between my feedback and their opinions. Whola source code files became fatter and thicker.
OK, now this is someone Else's source code, I have zero contribution, how can I do this comment block, Intellectual property rights violation :). Then came Judge Sotomayar's fav., a wise programmer will make better choice in life than an average programmer.
There is a plug-in for Eclipse called Jupiter. What a thought process by these folks. Check this tool out, awesome tool that will solve my problem to give feedback and track my changes. Jupiter is a Google code hosted open source tool.
It has one of the easiest plug-in integration. Installation was least painful for me and when I bought my workbench back, cool I got the plug-in installed and ready to be used.
WorkBench# 1 WorkBench Diagram # 1
Now let us talk about using it, once your workbench comes up, you might be able to see a small icon next to your print button of IDE. That is the magic button to do analysis. Jupiter basically allows three modes of operation,
Individual Phase.
Team Phase.
Rework Phase.
Am going to use the Common's workbook source code examples for showing the screens.
Individual/TeamWork Phase- In this phase a reviewer will be able to analyze independent files, track changes and submit it for development team. Here is a walkthro' for this task,
Step 1) Click the jupiter analysis drop down icon, select Individual phase, put in a good revision-id and description.
Step 2) Select the Java files that you would want to review.
Step 3) Put in a name for the reviewer- I put my name for our use-case and finally author of review session. Click finish you are done.
WorkBench #2 WorkBench #2
All errors that Jupiter can identify will show up in your jupiter review table window view. Clicking it will give an option to log it into the review editor. That's it you are done. When the source code owner looks at the code, he will be clicking the Jupiter icon and select rework phase. Dang he can review your inputs and will be able to close, reopen and keep the case for more clarification. No freaking intrusive comments, no hijack of original source code, clean neat way to track changes.
WorkBench #3 WorkBench #3
What a money saver and time saver. I was really impressed using this tool.