-
Bug
-
Resolution: Unresolved
-
Minor
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
- relates to
-
JENKINS-61855 Doxygen parser doesn't detect Doxygen Warnings
-
- Open
-
-
JENKINS-64657 Doxygen Error messages not parsed
-
- Resolved
-
Hi drulli and thebro - 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!