Hi Alexander I'm happy to see that Eclipse is now using Sonar and the Linux Tools project is using it, too. It's a great tool to statically analyse the quality of the source code. We (LTTng guys) have been using Sonar internally for a while and I was responsible for the setup.
I noticed in the Sonar results at Eclipse that the test plug-ins are also analysed. This can be avoided by adding an exclusion pattern to the sonar properties. Just add -Dsonar.exclusions="**/tests/**,**/test/**,**/stubs/**" to the "Additional properties" of the Sonar advanced configuration section of the Hudson job. Note that this pattern works well for all LTTng test plugins. Just for curiosity, which code coverage plug-in for Sonar is used at Eclipse? I always had to use JaCoCo for Eclipse plug-ins. All others, I wasn't able to get it work. Please let me know. Best Regards Bernd On Fri, Nov 2, 2012 at 8:26 AM, Aleksandar Kurtakov <akurt...@redhat.com> wrote: > Hi everyone, > We have sonar functional for Linux Tools. See > https://dev.eclipse.org/sonar/dashboard/index/org.eclipse.linuxtools:linuxtools-parent > . We don't look good in the code coverage area 16.1% branch coverage so > everyone please pay bigger attention to it and let's improve our testing for > the 2.0 release significantly. > P.S. LTTng guys, I know master doesn't make much sense for you but with 1.2 > release coming soon I would prefer to not configure one more job just for one > month. > > Alexander Kurtakov > Red Hat Eclipse team > > _______________________________________________ > linuxtools-dev mailing list > linuxtools-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/linuxtools-dev _______________________________________________ linuxtools-dev mailing list linuxtools-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
