| commit | 9867f9c2142355ae958f9eeb8fb96811082c8812 | [log] [tgz] |
|---|---|---|
| author | sameb <sameb@google.com> | Mon Feb 02 12:45:25 2015 -0800 |
| committer | Sam Berlin <sameb@google.com> | Tue Feb 03 18:07:07 2015 -0500 |
| tree | fb4ee51e5e4bfead67e2951c74958cdfe8b29194 | |
| parent | f11bf2d26ccd07e72805b789b33d855e223b1ed7 [diff] |
Implement my old patch for issue #366, with some tweaks. This does the following: * Fixes @Provides injection so that parameters are checked for nullability. By default this will error. The flag is named: guice_check_nullable_provides_params and can be set to ERROR, WARNING or IGNORE. * Adds InjectionPoint.forMethod to build an InjectionPoint off an arbitrary method. * Adds Binder.getProvider(Dependency) to a get a Provider for a given dependency (with all its nullability & injection points maintained). * Update ProviderLookup to accept a Dependency in addition to a Key. This is in preparation for two things: 1) Allowing multibindings/mapbindings/optionalbindings to be specified as annotations on methods in a module. 2) Adding a dagger compatibility module. ... the general idea will be that I'll also add a hook into ProvidesMethodModule somehow to look at arbitrary other annotations and let folks process them specially. ------------- Created by MOE: http://code.google.com/p/moe-java MOE_MIGRATED_REVID=85353820
- core/src/com/google/inject/Binder.java[diff]
- core/src/com/google/inject/internal/Errors.java[diff]
- core/src/com/google/inject/internal/InjectorImpl.java[diff]
- core/src/com/google/inject/internal/InternalFlags.java[diff]
- core/src/com/google/inject/internal/LookupProcessor.java[diff]
- core/src/com/google/inject/internal/ProviderMethodsModule.java[diff]
- core/src/com/google/inject/spi/Elements.java[diff]
- core/src/com/google/inject/spi/InjectionPoint.java[diff]
- core/src/com/google/inject/spi/ProviderLookup.java[diff]
- core/test/com/google/inject/spi/ProviderMethodsTest.java[diff]
- bom/
- core/
- examples/
- extensions/
- jdk8-tests/
- latest-api-diffs/
- lib/
- util/
- .gitattributes
- .gitignore
- .travis.yml
- build.properties
- build.xml
- common.xml
- CONTRIBUTING.md
- COPYING
- pom.xml
- README.md
Guice
Now, out in 4.0 Beta5!
Documentation: User Guide, 3.0 javadocs, Latest javadocs
Continuous Integration: 
Mailing Lists: User Mailing List, Developer Mailing List
License: Apache 2.0
Put simply, Guice alleviates the need for factories and the use of new in your Java code. Think of Guice's @Inject as the new new. You will still need to write factories in some cases, but your code will not depend directly on them. Your code will be easier to change, unit test and reuse in other contexts.
Guice embraces Java's type safe nature, especially when it comes to features introduced in Java 5 such as generics and annotations. You might think of Guice as filling in missing features for core Java. Ideally, the language itself would provide most of the same features, but until such a language comes along, we have Guice.
Guice helps you design better APIs, and the Guice API itself sets a good example. Guice is not a kitchen sink. We justify each feature with at least three use cases. When in doubt, we leave it out. We build general functionality which enables you to extend Guice rather than adding every feature to the core framework.
Guice aims to make development and debugging easier and faster, not harder and slower. In that vein, Guice steers clear of surprises and magic. You should be able to understand code with or without tools, though tools can make things even easier. When errors do occur, Guice goes the extra mile to generate helpful messages.
For an introduction to Guice and a comparison to new and the factory pattern, see Bob Lee's video presentation. After that, check out our user's guide.
We've been running Guice in mission critical applications since 2006, and now you can, too. We hope you enjoy it as much as we do.
