aosp12/external/guice
hcl 7be3fd486c init from android-12.1.0_r8 2023-01-09 17:11:35 +08:00
..
bom init from android-12.1.0_r8 2023-01-09 17:11:35 +08:00
core init from android-12.1.0_r8 2023-01-09 17:11:35 +08:00
examples/src/example/xml init from android-12.1.0_r8 2023-01-09 17:11:35 +08:00
extensions init from android-12.1.0_r8 2023-01-09 17:11:35 +08:00
jdk8-tests init from android-12.1.0_r8 2023-01-09 17:11:35 +08:00
latest-api-diffs init from android-12.1.0_r8 2023-01-09 17:11:35 +08:00
lib init from android-12.1.0_r8 2023-01-09 17:11:35 +08:00
util init from android-12.1.0_r8 2023-01-09 17:11:35 +08:00
.gitattributes init from android-12.1.0_r8 2023-01-09 17:11:35 +08:00
.gitignore init from android-12.1.0_r8 2023-01-09 17:11:35 +08:00
.travis.yml init from android-12.1.0_r8 2023-01-09 17:11:35 +08:00
Android.bp init from android-12.1.0_r8 2023-01-09 17:11:35 +08:00
CONTRIBUTING.md init from android-12.1.0_r8 2023-01-09 17:11:35 +08:00
COPYING init from android-12.1.0_r8 2023-01-09 17:11:35 +08:00
CleanSpec.mk init from android-12.1.0_r8 2023-01-09 17:11:35 +08:00
METADATA init from android-12.1.0_r8 2023-01-09 17:11:35 +08:00
MODULE_LICENSE_APACHE2 init from android-12.1.0_r8 2023-01-09 17:11:35 +08:00
NOTICE init from android-12.1.0_r8 2023-01-09 17:11:35 +08:00
OWNERS init from android-12.1.0_r8 2023-01-09 17:11:35 +08:00
README.md init from android-12.1.0_r8 2023-01-09 17:11:35 +08:00
build.properties init from android-12.1.0_r8 2023-01-09 17:11:35 +08:00
build.xml init from android-12.1.0_r8 2023-01-09 17:11:35 +08:00
common.xml init from android-12.1.0_r8 2023-01-09 17:11:35 +08:00
pom.xml init from android-12.1.0_r8 2023-01-09 17:11:35 +08:00

README.md

Guice

Latest release: 4.1

Documentation: User Guide, 4.1 javadocs, Latest javadocs
Continuous Integration: Build Status
Mailing Lists: User 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.

jolt award