This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I write lot of java code everyday. Sometime in hurry I forget to close the resources (connection,file,etc,) in JAVA6 and this causes memory leak issues. I am looking for an eclipse plugin which can complain for these minor mistakes. Also I am looking for some more eclipse plugins which can improve my source code quality like naming conventions, code redundancy, complexity, too long code outside methods, etc,.
I found some plugins on google itself like FINDBUGS, CHECKSTYLE, PMD, etc,.
Please suggest me a best plugin which can perform all above mentioned activities. Also please post the URL to watch that plugin demo.
Sonar runs Findbugs, PMD and CheckStyle internally as well and shows graphs using these aggregate data. Moreover, one can easily integrate Sonar with CI servers like Jenkins and TeamCity to view these reports.
Navneet Sharma wrote:I write lot of java code everyday. Sometime in hurry I forget to close the resources (connection,file,etc,) in JAVA6 and this causes memory leak issues. I am looking for an eclipse plugin which can complain for these minor mistakes.
That statement is a contradiction. If these "minor mistakes" cause problems, then plainly they aren't "minor", are they?
The best way to stop problems, as any QA zealot will tell you, is prevention, not control.
Code checkers - even good ones - may be able to stop some problems, but they won't stop them all; and they certainly won't make you a better programmer. And my worry is that it will become a crutch.
So, my advice: Slow down, and stop making these mistakes. You must have heard about the Tortoise and the Hare; well, programming is thought, not code.
Isn't it funny how there's always time and money enough to do it WRONG?
Articles by Winston can be found here
Before writing error prone code first get some knowledge about how to write a good piece of code.You can discuss with QA people or follow some check list or get reviewed the code with senior.Make this thing a habit.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com