Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-60469

Doxygen parser not detecting error

    Details

    • Similar Issues:

      Description

      The new doxygen parser which uses the

      Gcc4CompilerParser

      does no longer detect errors in "old style".

      I assume its from a doxygen subtask (plantUML)

      which was detected by the old

      DoxygenParser.

       

      The error looks like:

      Error line 22 in file: C:\projects\Doxygen\html\inline_umlgraph_3.pu

      Some diagram description contains errors

       

        Attachments

          Issue Links

            Activity

            Hide
            jarredparrett Jarred Parrett added a comment -

            Hi  Ulli Hafner and Kevin Broselge - I am working on this and have been able to reproduce and narrow it down to more than the patterns contained above. I found the following are picked up by the previous REGEX and not by the present GCC_WARNING_PATTERN as in the GCC4COMPILER.java. In working on this, there seems to be two approaches to fix it. On one hand, the regex could be rewritten to include the necessary missed lines or the two REGEX could be concatenated by way of '|'. There shouldn't be much  - to none - efficiency loss with the concatenation. Can I ask your thoughts on this?

            thanks,

            Jarred

            Contained by DOXYGEN_WARNING_PATTERN and not GCC_WARNING_PATTERN:{{Notice: }}

            Output directory `doc/doxygen/framework' does not exist. I have created it for you.

            <unknown>:1: Detected potential recursive class relation between class sofa::core::componentmodel::collision::Contact::Factory and base class Factory< std::string, Contact, std::pair< std::pair< core::CollisionModel *, core::CollisionModel * >, Intersection * > >!

            <unknown>:-1: Warning: Found unknown command `\TODO'

            error: Could not read image `/home/user/myproject/html/struct_foo_graph.png' generated by dot!

             

            Show
            jarredparrett Jarred Parrett added a comment - Hi  Ulli Hafner and Kevin Broselge - I am working on this and have been able to reproduce and narrow it down to more than the patterns contained above. I found the following are picked up by the previous REGEX and not by the present GCC_WARNING_PATTERN as in the GCC4COMPILER.java. In working on this, there seems to be two approaches to fix it. On one hand, the regex could be rewritten to include the necessary missed lines or the two REGEX could be concatenated by way of '|'. There shouldn't be much  - to none - efficiency loss with the concatenation. Can I ask your thoughts on this? thanks, Jarred Contained by DOXYGEN_WARNING_PATTERN and not GCC_WARNING_PATTERN: {{Notice: }} Output directory `doc/doxygen/framework' does not exist. I have created it for you. <unknown>:1: Detected potential recursive class relation between class sofa::core::componentmodel::collision::Contact::Factory and base class Factory< std::string, Contact, std::pair< std::pair< core::CollisionModel *, core::CollisionModel * >, Intersection * > >! <unknown>:-1: Warning: Found unknown command `\TODO' error: Could not read image `/home/user/myproject/html/struct_foo_graph.png' generated by dot!  
            Hide
            drulli Ulli Hafner added a comment -

            The previous regexp caused a lot of exceptions on some input texts, so I needed to remove that parser. If you find a better regexp please go ahead. One way would be to add an additional or to the Gcc regexp. Maybe an even better thing would be to create an additional parser for the missing pieces.

            Show
            drulli Ulli Hafner added a comment - The previous regexp caused a lot of exceptions on some input texts, so I needed to remove that parser. If you find a better regexp please go ahead. One way would be to add an additional or to the Gcc regexp. Maybe an even better thing would be to create an additional parser for the missing pieces.
            Hide
            jarredparrett Jarred Parrett added a comment -

            Interesting - gotcha I might try my hand at creating a new parser for Doxgen. Do you have any resources you might recommend I take a look at beyond looking at other parser classes? Thank you for the feedback

            Show
            jarredparrett Jarred Parrett added a comment - Interesting - gotcha I might try my hand at creating a new parser for Doxgen. Do you have any resources you might recommend I take a look at beyond looking at other parser classes? Thank you for the feedback
            Hide
            drulli Ulli Hafner added a comment -

            No, I think most parsers are a kind of mutation of an existing parser...

            Show
            drulli Ulli Hafner added a comment - No, I think most parsers are a kind of mutation of an existing parser...

              People

              • Assignee:
                Unassigned
                Reporter:
                thebro Kevin Broselge
              • Votes:
                1 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated: