I discussed the same topic with KK already. I would like to prevent all "Jenkins.getInstance....." lookups and replace them with dependency injection, but only _some_ jenkins components are managed by Guice, and do support this. Jenkins is not actually running in a CDI-like context where you could @Inject anything, just partially using Guice.
2014-10-06 10:37 GMT+02:00 Marc Carter <[email protected]>: > Not a word from anyone :) ? I'll assume that is "No and so far over the > horizon that you should delete your experimental branch" > > Perhaps after three years, the codebase has moved on and it is reasonable > to resurrect the old code branch(es) and implement this feature? What were > the final limiting factors that stopped it going mainstream at the time? > > Marc > > On Sunday, 21 September 2014 14:52:43 UTC+1, Marc Carter wrote: >> >> Hi all, >> >> There were plenty of conversations dating from 2011 on this topic but >> everything has since gone quiet. I see Guice is included as a direct >> dependency of jenkins-core but is hardly mentioned in the code and JSR-330 >> annotations don't seem to "just work" in plugin extensions, descriptors >> etc. Presumably it is not there for the benefit of general plugins or I'm >> just not doing it right ( >> https://github.com/JoelJ/ez-templates/commit/830001ee4593fa1f395a7c3bb4981e119ac85e13 >> ). >> >> Can someone advise please? >> >> Marc >> > -- > 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]. > For more options, visit https://groups.google.com/d/optout. > -- 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]. For more options, visit https://groups.google.com/d/optout.
