|
||||||||
|
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.
Sorry, I should have written a more detailed question...
Actually this message is there so that a user (like you) will create a bug report to force me to do a Checkstyle upgrade in the plug-in. (This happens if a newer Checkstyle version produces an unknown warning that is not yet described in my plugin). However, in your case an upgrade will not help, since you are not using Checkstyle.
So what should we do?
a) Include the coffeelint messages into the plug-in (is that possible?)
b) Don't write the "missing description" message at all (even for original checkstyle files)
c) Add a coffeelint parser to the warnings plug-in (then no descriptions are required)
d) Write a new plug-in for coffeelint (based on analysis core)