Closed vrenjith closed 7 years ago
@Jimilian - are you happy to approve the changes?
@nickgrealy To be honest, nope. I hope that @vrenjith can say why do we need to call parent method. Even in case then this method is not doing anything (empty).
I very appreciate any PR, so, we can merge it and after that I will remove code that I don't like. But maybe @vrenjith knows something about these methods that I don't. Also tests are missed :(
@Jimilian - no problem, I'll wait until those changes have been discussed (tests would be good!) and let you perform the merge. 👍
I haven't checked the implementation of ItemListener
and to be on the safe side I assumed it is always better to call the parent. Hence retained the super
calls. But if @Jimilian thinks that it is unnecessary, I can just remove them and update the PR
@vrenjith Yes, it would be perfect. As you can see in any other listener in this plugin (i.e., https://github.com/jenkinsci/groovy-events-listener-plugin/blob/master/src/main/groovy/org/jenkinsci/plugins/globalEventsPlugin/GlobalRunListener.java) we don't call parent function. Otherwise it would be broken Observer pattern.
@vrenjith I uncommented checking java version and merged you PR. Thanks a lot for passion and patience:)
@nickgrealy, could you release new version, please? We found a beautiful use case there this feature could rock :)
@Jimilian yep sure! Give me 15 mins...
@Jimilian - just checking, are you happy with the state of the current master branch?
There's been a lot of changes since the last release - dc5f51d
Including this line - https://github.com/jenkinsci/groovy-events-listener-plugin/blob/master/build.gradle#L82 - which re-introduces your issue - https://github.com/jenkinsci/groovy-events-listener-plugin/issues/21
@nickgrealy Oups, I forgot about https://github.com/jenkinsci/groovy-events-listener-plugin/blob/master/build.gradle#L82.
Changes proposed in this pull request:
ItemListener
for listening for configuration changes@nickgrealy