Description

When analyzing a flex project, we are able to see correctly the mxml files that are stored at root level, but not files that are stored in a directory.
I added the analysis for mxml as well as for as (by the way it may be good to analyze by default those two extensions to avoid getting questions about that).
I attached a simple project where the file FlexSonarSourceMXML at root level is correctly displayed after the analysis but the file FlexSonarSourceMXML1 located in directory pk1

I also attached a screenshot of sonar analysis where it appears that sonar is considering the second file differently.

Concerning first, our issue is not for the as files as those are correctly processed by the system (here we wanted to build a quick project and may have forgotten about that) but our concern is on the analysis of the mxml files.
Yes we have defined the sonar.flex.file.suffixes with as and mxml and that was also my second comment, that maybe by default you should get both as and mxml files to be analyzed.

So with a setup that seems correct (at least it allows us to see the mxml file stored at root level) we are not able to see a file stored onder a subfolder. Both are correctly analysed as we get issues reported on that other file, it is more issues with the display mechanism.

stephane Renou
added a comment - 29/Mar/11 9:18 AM Concerning first, our issue is not for the as files as those are correctly processed by the system (here we wanted to build a quick project and may have forgotten about that) but our concern is on the analysis of the mxml files.
Yes we have defined the sonar.flex.file.suffixes with as and mxml and that was also my second comment, that maybe by default you should get both as and mxml files to be analyzed.
So with a setup that seems correct (at least it allows us to see the mxml file stored at root level) we are not able to see a file stored onder a subfolder. Both are correctly analysed as we get issues reported on that other file, it is more issues with the display mechanism.