On Fri, Nov 20, 2015 at 7:58 AM, Kanstantsin Shautsou <[email protected]> wrote: > With annotations in different parts of > code you can't handle sequence of actions during start/stop. Spreading many > start/stop/post-init hooks with annotations in different classes makes not > obvious lifecycle
Nothing is stopping you from adding multiple `@Initializer`s (and/or `@Terminator`s) in a single class if you find that clearest, though in my experience each `@Initializer` is usually best placed in a class related to its actual function, which is likely unrelated to any others that happen to be present in the same plugin. So I do not buy this as an argument for retaining `Plugin`. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3PKpKYbRnZ2yEHFHWCt4qCc7Lwr_GRcuowcc6PUD3hxg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
