All Versions
Latest Version
Avg Release Cycle
33 days
Latest Release
173 days ago

Changelog History
Page 3

  • v2.21 Changes

    January 16, 2019
    • ๐ŸŽ Build performance improvements (174a7a9)
      • Separately, there may be an increase in build times for opensource users using javac9 or javac10. Neither javac8 or javac11 should be affected. (96fcce8)
    • ๐Ÿ†• New validation:
      • Installing a module with scoped bindings that an ancestor component has also installed is now an error. (4695ff5)
      • A warning is now reported if an explicit binding conflicts with an @Inject binding in an ancestor component. This was never intended to be supported but never checked. Adds a flag to control whether that is a warning or an error. (7f5500f)
      • Installing a @ProducerModule in a @Subcomponent that is already installed in a parent (or earlier ancestor) component is now an error. It is also an error to repeat a @Module that has a binding in @ProductionScope. (68b2153)
    • SPI
      • New method: ComponentNode.isSubcomponent() (b6b9dca)
    • Producers
      • Deprecated dagger.producers.internal.Producers.immediateProducer() and dagger.producers.internal.Producers.immediateFailedProducer() in favor of newly added methods with the same names in dagger.producers.Producers (a4914c6) (added in 50d7010)
    • Properly generate components when qualifiers are generated (ab9cdbc)
    • Dagger itself now uses more Dagger (97fce1e)
  • v2.20 Changes

    December 20, 2018
    • Peformance improvements in annotation processing (8012ab5)
    • Report duplicate bindings only once, not once per request. (623461f)
    • ๐Ÿ‘‰ Make sure all processing steps defer elements properly if they have missing types. (3b0fcc8)
    • ๐Ÿ‘‰ Make @ProductionComponent have runtime retention so tools can interpret it like all of the other component annotations (fff65e3)
    • 325b516:
      • Add module-level validation. When -Adagger.moduleBindingValidation=ERROR or =WARNING is set, then each module is processed as a kind of component (without generating any code) in order to validate the bindings installed by it and all included modules. Any binding graph errors, such as duplicate bindngs (but not including missing bindings), will be reported as errors or warnings depending on the option.
    • Report map multibinding contribution errors once regardless of whether the map is requested as Map<K, V>, Map<K, Provider<V>>, or Map<K, Producer<V>>. (350368e)
    • c7e7c4f:
      • Fixes two bugs related to @ProductionScope bindings:
      • Where modules with @ProductionScope bindings are installed in multiple components in the same component ancestry, the binding is now resolved only once and only in the rootmost component.
      • When @Inject bindings with @ProductionScope are referenced in a binding graph, the binding is now resolved in the rootmost @ProductionScope component.
    • 221f000:
      • code can no longer use the AndroidInjector.Factory<? extends Activity> format to bind injector factories. See and the 2.19 release notes for information on how to migrate.
      • Adds an ErrorProne refactoring for migrating from AndroidSupportInjectionModule (which now is functionless) to AndroidInjectionModule. See these docs for how to apply the refactoring to your codebase if you're on dagger-compiler-2.20.
    • โœ‚ Removed dagger.releaseablereferences (a72c342)
    • โœ‚ Removed the -Adagger.floatingBindsMethods flag added in 2.17 ([email protected]) (bc8dd5b)
  • v2.19 Changes

    October 29, 2018
    • has a new format for binding AndroidInjector.Factorys:
      • Instead of returning AndroidInjector.Factory<? extends Activity> (or Service, Fragment, etc), return just AndroidInjector.Factory>
      • Instead of using @ActivityKey (or @ServiceKey, @FragmentKey, etc), use @ClassKey. The map keys (with the exception of @AndroidInjectionKey are now deprecated
      • If you use @ContributesAndroidInjector, there's nothing to do. We have updated the output to match the new format
      • We have provided an ErrorProne refactoring for migrating to the new format of binding AndroidInjector.Factorys with See these docs for how to apply the refactoring to your codebase if you're on dagger-compiler-2.19. (02dc4a7)
      • In the next release (2.20), we will remove the old format. This will allow us to support AndroidX packages better.
      • For the complete docs, visit
    • Avoid some thrown errors during Dagger compilation for invalid modules. (4df5adf)
    • ๐Ÿ›  Some formatting fixes even when the formatter is turned off
  • v2.18 Changes

    October 19, 2018
    • Producers:
      • Added @CancellationPolicy annotation, which can be used to make a production component or subcomponent allow cancellation of its subcomponent(s) to propagate up to it and cancel its nodes as well. (f5c04a5)
      • Producer cancellation is now deterministic; cancelling an entry point of a production component will now ensure that it cancels all running tasks for that component and prevents any further tasks for that component from starting. For components with more than one entry point, this does mean that cancelling one entry point will cancel all entry points for the component. For production subcomponents, cancellation of a subcomponent entry point will not propagate cancellation to tasks owned by an ancestor component. (ea48dfd)
    • ๐Ÿ‘ Better Errors:
      • Change constructor bindings and dependency requests from void package.Class.<init>(params) to package.Class(params), which looks more like how Java users think of constructors. (d31943c)
      • Report errors on members injection component methods and MembersInjector requests that have qualifiers. (3be3073)
      • Report erroneous bindings once for all their incoming dependency requests, instead of once for each incoming dependency request. If a binding is owned in more than one component, it will still be reported once for each component that owns it. (beefa94)
      • Report errors when members-injecting primitives and arrays in component methods as well as unused bindings. (d6a0db3)
      • Report binding graph errors once at the root component, not once per entry point from which the error is reachable. Include the dependency trace from one entry point only, and list the other entry points from which the error is reachable. (46f315f)
      • Report errors for dependency requests with multiple qualifiers in @Provides and @Produces methods and component entry points instead of throwing IllegalArgumentException. (da2e1f0)
      • Adds a support version of DaggerDialogFragment (47be5db)
    • ๐Ÿ— Build perf:
      • Add an option to disable formatting of generated code: -Adagger.formatGeneratedSource=disabled (6814a21)
      • Add support for gradle's incremental annotation processing. This can be enabled by passing -Adagger.gradle.incremental to javac (cd83b30)
      • Originating elements are now reported to the Filer (baf2357)
      • Improvements in processing time (b0786a5)
    • ๐Ÿ› Bug fixes:
      • Fixes bug in fast init (b/116268009). (be9493d)
      • Report an error (instead of throwing IAE) if a component builder method has a primitive parameter and is not annotated with @BindsInstance. (5c69aab)
      • Avoid IncompatibleClassChangeError in DiagnosticReporterImpl when guava-android is on the processor path. (efb042d)