|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Thanks for your prompt work, Ulli. Let be make sure that I understand you correctly:
1. Even though my config.xml had `<parserName>Apple LLVM Compiler (Clang)</parserName>`, the correct parser was still being used after I updated from warnings 4.23 to 4.24.
2. The display of "Acu COBOL" on editing my config after updating to warnings 4.24 was a UI-only glitch.
3. Suppose that, unaware of this issue and running warnings 4.24, I had edited only another aspect of my config (say, the log rotator) and saved the config? Would the parser name have stayed as "Apple LLVM Compiler (Clang)" or would it have been changed to "Acu COBOL"? Just trying to cover all bases.
Regards,
Richard.