Adding option -Dsonar.exclusions=**/*.aj produce unexpected results

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.12
  • Fix Version/s: 2.1
  • Component/s: None
  • Labels:
    None

Description

Appending -Dsonar.exclusions=*/.aj to Sonar command line produces unexpected results. On project dashboard there are only a few values that are filled: LoC, Comments and Complexity.
There are 0 reported violations, no test result nor test coverage, no duplication, and no source code is visible in drill down (see attached screenshot).

There is no error in Maven console output.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Freddy Mallet added a comment -

Bug has been reproduced on my side. Looks like the exclusion pattern "*/.aj" is not correctly interpreted. We're trying to fix it in Sonar 2.1.

Show
Freddy Mallet added a comment - Bug has been reproduced on my side. Looks like the exclusion pattern "*/.aj" is not correctly interpreted. We're trying to fix it in Sonar 2.1.
Hide
Permalink
Freddy Mallet added a comment -

BYW, on java side, it's not necessary to define such exclusion pattern, as Sonar only analyse .java files.

Show
Freddy Mallet added a comment - BYW, on java side, it's not necessary to define such exclusion pattern, as Sonar only analyse .java files.

People

  • Assignee:
    Simon Brandhof
    Reporter:
    Julien HENRY
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: