Details

    • Patch Submitted:
      Yes
    • Number of attachments :
      3

      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.

        Activity

        Hide
        Evgeny Mandrikov added a comment -

        Hi Stephane,

        First of all - I wonder why your code doesn't contain "package" declarations ( http://livedocs.adobe.com/flex/3/html/help.html?content=basic_as_2.html ) ?
        Second - do you know about property "sonar.flex.file.suffixes" (Settings -> Flex -> File suffixes) ?

        Show
        Evgeny Mandrikov added a comment - Hi Stephane, First of all - I wonder why your code doesn't contain "package" declarations ( http://livedocs.adobe.com/flex/3/html/help.html?content=basic_as_2.html ) ? Second - do you know about property "sonar.flex.file.suffixes" (Settings -> Flex -> File suffixes) ?
        Hide
        stephane Renou added a comment -

        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.

        Show
        stephane Renou added a comment - 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.
        Hide
        Jorge Castello added a comment -

        Same for us here. We have a Flex module wich contains the following structure:

        (1) /FiscalizacionModule.mxml
        (2) /es/foo/bar/view/StringDateFieldChangeEvent.as
        (3) /es/foo/bar/view/StringTextInputFieldChangeEvent.as
        (4) /es/foo/bar/view/FechaPieReport.mxml
        (5) /es/foo/bar/model/ModelLocatorFiscalizacionPrevia.as
        (6) /es/foo/bar/model/Nomina.mxml

        We can only see sources (violations, coverage and so) on files 1,2,3 & 5, but not for 4 & 6

        Sonar 2.5, Sonar Flex Plugin 0.3.1

        Show
        Jorge Castello added a comment - Same for us here. We have a Flex module wich contains the following structure: (1) /FiscalizacionModule.mxml (2) /es/foo/bar/view/StringDateFieldChangeEvent.as (3) /es/foo/bar/view/StringTextInputFieldChangeEvent.as (4) /es/foo/bar/view/FechaPieReport.mxml (5) /es/foo/bar/model/ModelLocatorFiscalizacionPrevia.as (6) /es/foo/bar/model/Nomina.mxml We can only see sources (violations, coverage and so) on files 1,2,3 & 5, but not for 4 & 6 Sonar 2.5, Sonar Flex Plugin 0.3.1
        Hide
        Eugene Zadyra added a comment - - edited

        Patch to fix this issue attached

        Show
        Eugene Zadyra added a comment - - edited Patch to fix this issue attached
        Hide
        stephane Renou added a comment -

        hello, is there any plan on integrating this patch into an official release?

        Show
        stephane Renou added a comment - hello, is there any plan on integrating this patch into an official release?
        Hide
        Evgeny Mandrikov added a comment -

        Hi Eugene,
        In this patch I didn't found any unit test to verify new behaviour.
        May I ask you to provide new one with included unit tests?

        Show
        Evgeny Mandrikov added a comment - Hi Eugene, In this patch I didn't found any unit test to verify new behaviour. May I ask you to provide new one with included unit tests?
        Hide
        Fabrice Bellingard added a comment -

        SONARPLUGINS-1666 solves this issue.

        Show
        Fabrice Bellingard added a comment - SONARPLUGINS-1666 solves this issue.
        Hide
        Freddy Mallet added a comment -

        Manually tested

        Show
        Freddy Mallet added a comment - Manually tested

          People

          • Assignee:
            Fabrice Bellingard
            Reporter:
            stephane Renou
          • Votes:
            3 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: