On Wed, Jan 7, 2015 at 6:10 AM, Tom Fennelly <tom.fenne...@gmail.com> wrote: > As for using the @Extension annotation, yes it would be a little less > invasive but my original thinking (may no longer be valid having the benefit > of hindsight) was that doing it through extension made it easier
You mean, doing it through Plugin? > for us to > keep track of what plugins are theme contributors, and so, remove them from > the contributor list as the plugin is uninstalled. In hindsight though it > seems like plugins are not really uninstalled until after a restart Right, Jenkins does not support dynamic uninstallation. And if and when it is improved to do so, we would of course be providing an API to listen for extensions going away. > maybe @Extension would work I am pretty sure this should be an @Extension. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr14t6duwkEGkh3kPbNBWKhj4kDpLf%3Dp_hZQ3AbnBoKhYQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
