|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
Seems that I forgot to add a description of that parser. The code is already committed - I will publish a new release today...
BTW: Students of my tooling lecture are currently replacing all violation parsers with "native" warning-plugin parsers (the approach with delegating to the violations plug-in does not work with builds on slaves), see JENKINS-17794. So if you have a Stylecop result file that you are able to share for a unit test please attach the file to issue JENKINS-17794.