On Wed, Nov 18, 2015 at 1:21 PM, Kanstantsin Shautsou <[email protected]> wrote: > I thought it is right entry Point if somebody wants to use some plugin > specific actions as it obvious entry point for plugin
Maybe I am not understanding what you wrote, but why do you need to extend `Plugin` at all if you just want a class where you can put some general-purpose code used throughout the plugin? > I also thought that start/postInitialize is used to get earlier actions for > magic actions (i.e. alias XStream entries). You can do such things in `@Initializer`. (Sometimes people use `static` blocks in `Descriptor`s, in the particular case of XStream aliases pertaining to the corresponding `Describable`, though that idiom might break if we implement JENKINS-22050.) -- 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/CANfRfr0QBQrsugDB3txmxre07mzmcBFze0Vq%2BYyCkBMNGONRWg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
