Affects Version/s: FB-CONTRIB-1.0
Fix Version/s: FB-CONTRIB-1.1
Environment:Ubuntu 10.04.1LTS and Sun JDK 1.6.0_24
export MAVEN_OPTS="-XX:MaxPermSize=192m -XX:PermSize=192m -Xms1024m -Xmx1024m -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -Xss256k"
Number of attachments :
Originally I wanted to create an issue about OutOfMemoryError, but this is fbcontrib's problem and issue is here:
Originally I wanted to uninstall the plugin, but then I decided to only uncheck the problematic rule - and then I have seen that all the fb-contrib rules are already disabled ... but analysis has been done!
A few days before I upgraded the Sonar from 2.4.1 to 2.5 and then to 2.6.
Then I installed the fbcontrib plugin and successfully analyzed some projects - fbcontrib results are missing despite the analysis has been done.
Correct: deactivated rules should be skipped already when analyzing the classes
Now I: Classes are analyzed, but results of the deactivated rules are ignored.
Now II: Deactivated rule can crash the build
Now III: Deactivated rules slow down the maven build.
Now I uninstalled the fbcontrib sonar plugin.
1) Stacktrace in a part of the maven output
2) JConsole snapshot - about 20 minutes before the crash is analysed the only one subproject. About 40 minutes before took the analysis of another 20 subprojects of similar size and complexity. This is why I think that it is a blocker issue - it is fatal.