Eclipse India Summit '09

An eclipse carnival is hosted in Bangalore for the next two days.

The organizers of the hugely successful Great Indian Developer Summit, the Salt March Media and the eclipse based consulting firm ANCIT Consulting have joined hands together to create two days of eclipsing - The Eclipse Summit India, 2009.

This is conducted on 17th and 18th of July, 2009. Its exciting to be surrounded by eclipse hips and hops, bells and rings, yums and yummies for two days - technical presentations, get togethers, contests, evangelism etcetera.

For the last two years ANCIT consulting conduct the Eclipse Demo Camps in Bangalore. The demo camps have nurtured and patted my interest in Eclipse and has created atleast one more eclipse enthusiast.

For the next two days, tune to my blog to see the latest updates, events and news from the happening zone.

madhu

On the fly analysis of code!

Long long ago, I wrote my first java program in notepad. I wrote my helloworld program, saved and compiled it using 'javac'.

A few compiler errors!!!

I corrected those errors and executed the program. I was happy!

A few years later....

I met eclipse. I wrote my hello world java program using the jdt editor. As soon as I made an error, the java editor showed the errors in red jagged lines. I was excited. I no longer required to finish the entire program to see the compiler errors.

Years passed again! I started to write bigger programs. I started to use a few static analysis tools to make sure my code is of good quality. I use both PMD and Findbugs. But I feel as if I have gone a few years before. I feel as if I am using the notepad again.

To see the code analysis results, I need to complete the coding, then execute the static analysis tools. PMD and Findbugs together might show more than 100 errors.

It was good if the code analysis tools were integrated with JDT. If I type a piece of code, the code should be analysed by the tools on the fly and bring the results. The static analysis tool should not make the end user to wait till he/she manually triggers the analysis.

I could've raised an Eclipse bug in bugzilla if we had a static analysis tool in Eclipse group of projects. How about putting up the analysis logic in the JDT editor? But the code analysis job will be the specialization of static code analysis tools, not JDT. How about JDT exposes some interfaces which the static analysis tools can make use of?

Any thoughts / comments / action over this issue are welcome.

madhu