----- Original Message ----- > It only means that the matching java packages are not analysed by > Sonar. For example, no code violations (e.g findbugs) are reported in > Sonar for the matching packages. I prefer to have violation reports, > code coverage report and other reports only for the delivered source > code and not for the test code itself. The code coverage is based on > the test case execution and it's result. The -Dsonar.exclusions > doesn't omit the test execution and the code coverage report. Maybe > you can try it and see the difference. > OK, the exclusion pattern added so we can see the difference. On second thought I agree that it makes sense to fix violations in shipped code first and as we would not have very good results there it makes sense to concentrate effort their first. I still think that tests should obey the same results and it makes sense to me to remove the exclusions once we get good results in the shipped sources (if ever we achieve that).
Alexander Kurtakov Red Hat Eclipse team _______________________________________________ linuxtools-dev mailing list linuxtools-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
