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.
We are using Maven 3 for building our multi module app, and we had installed Sonar 2.8 and have a sonar build working in our CI environment that would publish the results to the sonar. Unfortunately, that sonar build stopped working. I investigated and I found that we had introduced an unit test that takes a long time to run. the Maven sonar plugin opens a connection to the database server and keeps it open while the test is running. Eventually, the connection times out while the unit test is running, and sonar bombs.
I googled around and it looks like this was a bug in Sonar that was fixed recently. So, I installed SOnar 3.5.1 on a server. I assumed that I had to use a maven sonar 3.5.1 plugin, but all their documentation says that we should put 2.0 in the version number of the plugin. Which is kind of screwy to me. I assumed that the plugin is opening a connection to the database, and unless I don;t upgrade the plugin, I will still get the problem. So, how do I upgrade the plugin
Is my assumption wrong? is the plugin doing like web service calls to the server, and the server opens DB connections?
The test is running right now. I should know whether it really worked or not. It did run some long running tests but hasn;t hit the one it was failing on. So, how does it work?
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