|
||||||||
|
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.
Even RuntimeExceptions can be mentioned in Javadoc. IMHO they even should be mentioned in a case like you expect it - i.e. that throwing a RunnerAbortedException from RunListener will abort the build.
In fact, the only usecase mentioned in RunListener is producing log messages which is a pure 'consuming' use case which is very different from a 'vetoing' usecase like you seem to expect.
Note that I'm not generally saying that what you expect from RunListener is false. It's just that I can't see it in the interface as it is documented currently.