Ability to exclude source folders from source code analysis (the same way it's possible to exclude some packages for instance)

I wouldn't say "rather", but an additional ability to exclude root source folders would be greatly appreciated.

Most of our project's modules have separate "gensrc" and "src" root source folders. We can't use the package exclusion method because the packages in both of the source folders are named the same to reflect their affiliation to each other.

I am having an issue where I have code in /src/test/java that has an issue but I can't exclude the code using sonar exclusions. This is the standard Maven source directory for test code. In order to support analysis on Maven projects that follow the standards it seems to me this issue must be addressed.

Indeed this is a must-have on our site. We have big amounts of generated code which normally does not meet any rules. As these violations are reported the "real" problems are not really visible. As the code is generated via Maven (and placed in target/generated-sources) it should be easily possible for the sonar-plugin to detect them and auto-generate and apply the according exclusions.

Afaik sonar is only able to exclude based on package/classname patterns because PMD and other tools are working on bytecode. On the other hand which class is generated and which is not is not readable out of the bytecode (even if the @generated-annotation is used - it is not a runtime annotation).

As a solution I could think of the following:

• The maven-plugin knows about the source-folders
• from all source-folders which are in target (or other configured name) (or as a positive list: which are in some named directories, defaults src/**) a list of classes (files) is made and used to build an exclusion-list
• This exclusion list gets merged with some eventually existing exclusions
• The exclusions are used when analyzing

I think this would at least lead to a 99% solution

Regards Michael

Can we hope a sonar.excludeSourceFolder in a next release?

Sorry Mickael, this is not planned for Sonar 3.4 but already for Sonar 3.5.

> Sorry Mickael, this is not planned for Sonar 3.4 but already for Sonar 3.5.

I'm glad to here this is planned! Thanks.

Are you aware of the regex based file filter plugin over at https://github.com/Obeo/fr.obeo.sonar.plugin.regexfilefilter
It provides a solution to exclude generated code by looking at the content of the file (not the source folder name).

Most of users will still use the standard inclusion/exclusion patterns. To prevent from misunderstanding of a new property, we're going to improve the format of existing exclusion properties. If they start with "file:", then the exclusions will relate to absolute path. A typical usage could be "file:*/src-gen//".

@Michael Keppler, this plugin is a good candidate for the plugin forge !

The exclusion of files based on absolut paths works well with "exclusion patterns" but not with "inclusion patterns".

Moreover the following items must be added to the "Wilcards" documentation :

• In "Following rules are applied":
  • file: to define a pattern based on the absolut path
• In "Examples:":
  • org/mycompany/* matches all files in the org/mycompany directory. ex: org/mycompany/Foo.java, org/mycompany/Bar.cs
  • org/*Model matches all files with Model in filename and in the org directory. ex: org/Model.java, org/FirstModel.php, org/ModelTest.cs
  • org/*/.cs matches all .cs files underneath the org directory . ex : org/Foo.cs, org/foo/Bar.cs, org/foo/bar/Baz.cs
  • file:**/generated/** matches all files whose one parent directory is 'generated'. ex: /../my_project/tmp/generated/org/castor/Model.java

Thanks for correcting that!

A shame I'm not developing Eclipse based stuff anymore

Keep up the good work guys!