-
Bug
-
Resolution: Fixed
-
Minor
-
None
So far as I can tell, the classloader used for searching for @Initializer annotations is constructed before the plugins are available, so it doesn't search plugin classes. As a result, one can't use @Initializer for any phase in plugins. It'd be handy if there was a way to do this - or a second annotation, say, @PluginInitializer, which did search plugins.
[JENKINS-5427] hudson.init.Initializer annotation does not work from within plugins
Priority | Original: Major [ 3 ] | New: Minor [ 4 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Workflow | Original: JNJira [ 135516 ] | New: JNJira + In-Review [ 186988 ] |
Workaround is to define a Plugin class and override start() or postInitialize().