Releases · google/dagger

Optimized generated @Components! We now inline many calls to @Inject constructors and @Provides methods when we don't need a Provider<T>.
Some optimizations to the dagger-compiler
java.util.Optional support for @BindOptionalOf
Releaseable References API for handling memory pressure for scoped bindings
Our first release of the dagger-android artifact
@Provides.Type is officially deprecated - see their javadoc for the appropriate alternatives. As per our Versioning docs, these will be removed in ~6 months
Bug fixes with optional bindings in subcomponents
Some generated factories are no longer implemented as enums, reducing code size for Android users

A few bugfixes

Create bindings for @Binds methods even when the RHS cannot be resolved
- Note: this may result in new duplicate or missing binding errors that were not previously detect.
Change ProducerToken to use Class#getCanonicalName instead of Class#toString to avoid extra string allocations.

@Provides methods are now allowed in @ProducerModules
New and better multibindings errors
Provider<Lazy<T>> can now be used to break dependency cycles.
Fixes bug where @Binds methods sometimes didn't contribute to multibindings in subcomponents
Fixes bug where generated factories had conflicting parameter names

Enables @Binds usage with multibinding annotations (@IntoSet, @ElementsIntoSet, and @IntoMap)
Adds @Multibinds API to replace @Multibindings interfaces
@Component.Builder methods for abstract modules are no longer allowed
Performance improvements for @IntoSet usage. Provided objects are no longer wrapped in a wasteful Collections.singleton()
Compilation speed improvements for large graphs
@Scopes are no longer allowed on @Produces methods
Adds state checking to scoped providers to make sure a circular dependency does not create multiple instances
Producers optimizations: Each @Produces method now generates 1 class instead of 2
Fix: Requests for Map<K, V> now include both @Provides @IntoMap and @Produces @IntoMap values

Adds @Binds API for delegating
one binding to another
Adds @IntoSet, @ElementsIntoSet and @IntoMap to replace @Provides(type = ...) and @Produces(type = ...)
Allow injection of Provider<Lazy<Foo>>
Report an error if a @Scope annotation is applied to an @Inject constructor
Remove the ability to set the production executor on a component builder.
Ensure that no binding methods are binding framework types.
New format of dependency traces in error messages
Fixed bug: Exception when a binding in a parent that is used only in a subcomponent depends on a binding in the subcomponent
Update to JavaPoet 1.6.1 and Google Java Format 1.0
- Fixes NoSuchMethodError from Issue #356

dagger.mapkeys moved to dagger.multibindings and all @MapKey
implementations now correctly have @Beta applied
Better error messages for multibindings
Compiler bug fixes!

Correctly handle @Components that inject generated types
Adds @ProductionSubcomponent and @ProductionScope
Allow the production Executor to be bound with @Production
Allow multiple scope annotations on components
A component's subcomponents’ (and their subcomponents’) simple names no longer need to be unique
Adds the ability to depend on subcomponent builders
GWT Integration
Producers monitoring
Multibindings for producers
Add common @MapKey annotations to dagger.mapkeys. These annotations are
not, but should be marked @Beta (since the @MapKey itself is beta).
Lots of bug fixes!

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.)

Releases: google/dagger