Skip to content
  1. Feb 10, 2012
    • Kohsuke Kawaguchi's avatar
      83ad02d9
    • Kohsuke Kawaguchi's avatar
      added doc · 61ec0fc6
      Kohsuke Kawaguchi authored
      61ec0fc6
    • Kohsuke Kawaguchi's avatar
      Revisited the way Guice creates an injector during unit test · a71d037b
      Kohsuke Kawaguchi authored
      The motivation of this is to enable test code to inject components from Jenkins, which means we need a single Injector that can see all of those, including @TestExtension and regular @Extension. Then I realized that the current implementation is broken, as it creates two independent Injectors. This has other undesirable side effects like @TestExtension components not being able to inject @Extensions, etc.
      
      I briefly experimented with hierarchical Injectors (where we first create Injector that loads @Extension then create another that loads @TestExtension as a child), but this was hard to get right as we have no control over which ExtensionFinder gets instantiated first --- we'd be at the mercy of SezPoz.
      
      So the eventual approach is to allow a single GuiceFinder to recognize multiple annotations. This also works well with our using child injector for installing plugins without restart
      a71d037b
  2. Feb 09, 2012
  3. Feb 08, 2012
  4. Feb 06, 2012
  5. Feb 04, 2012
  6. Feb 03, 2012
  7. Feb 02, 2012
  8. Jan 31, 2012
  9. Jan 30, 2012