Releases: google/dagger
Releases · google/dagger
Dagger 2.0.2
A patch release, most crucially including:
- A fix to the way processor validation of types is done that permits dagger to play
more nicely with other processors, avoiding over-validating aspects that it doesn't
need, which may yet not have been generated by other processors in a different round
of processing. - Some improved error reporting for edge-cases
- Fix to prevent incompatible versions of Guava on the classpath from blowing up processing
- Support a more robust set of types for map keys in map bindings (primitive types, etc.)
Dagger 2.0.1
A maintenance release fixing immediate issues following the Dagger 2.0 release, including:
- Speed up Graph Validation (reduce build times by 10s of seconds on sampled large projects)
- Generate correct code for
@MapKeyannotation types (beta) - Fix to properly emit code for class literal values in
@MapKeyannotations. - Fix for injecting component dependencies
- Fixes to generated code to account for differences in generics handling in ecg vs. javac.
- Subcomponents can now be abstract classes.
- Subcomponents now properly build the object graph in some cases involving explicit bindings
and (sub)components without scope. - Improve runtime performance of SetFactory (set multibindings)
- Other smaller fixes, refactorings, etc.
Dagger 2.0 Initial Release
The initial release of the 2.0 code-line, supporting:
@Componentinterfaces representing a custom API to access a graph of objects- JSR-330 injection automation using
@Injectsignals,@Qualifiers - Simple bindings of implementations to interfaces, custom provision of objects, and set-bindings
- Compile-time validation of graph structure (cycles, missing bindings, duplicate bindings)
- Generation of
- backing implementations for components
- factories for
@Injectconstructors and modules - members-injectors for
@Injectmethods and fields
- Beta support for
- Map bindings
- Producers