| commit | 07bcdbf2e0a9ce721565b536de34ec11aaf614e7 | [log] [tgz] |
|---|---|---|
| author | Neil Fuller <nfuller@google.com> | Tue Feb 23 16:59:20 2016 +0000 |
| committer | Neil Fuller <nfuller@google.com> | Tue Feb 23 16:59:42 2016 +0000 |
| tree | 2750b80f5a5a08dd0fb370d4ffd9a5a8025ce6de | |
| parent | 0678a34f05bbbcee7b16a29fa8aefae91e5bf359 [diff] |
Pin libraries needed by vogar tool to java 1.7 vogar still uses javac/dx by default. dx does not handle v52 class files. The default java version is going to switch to 1.8. This change pins the targets need by vogar to 1.7. Bug: 26753820 Bug: 27310428 Change-Id: I0f18bc98d3500828a09dbe5a4766940ee993b9fe
A fast dependency injector for Android and Java.
Dagger 2 is a compile-time evolution approach to dependency injection. Taking the approach started in Dagger 1.x to its ultimate conclusion, Dagger 2.0 eliminates all reflection, and improves code clarity by removing the traditional ObjectGraph/Injector in favor of user-specified @Component interfaces.
This github project represents the Dagger 2 development stream. The earlier project page (Square, Inc's repository) represents the earlier 1.0 development stream.
Both versions have benefitted from strong involvement from Square, Google, and other contributors.
Dagger is currently in active development, primarily internally at Google, with regular pushes to the open-source community. Snapshot releases are auto-deployed to sonatype's central maven repository on a clean build with the version 2.1-SNAPSHOT.
You can find the dagger documentation here which has extended usage instructions and other useful information. Substantial usage information can be found in the API documentation.
You can also learn more from the original proposal, this talk by Greg Kick, and on the dagger-discuss@googlegroups.com mailing list.
You will need to include the dagger-2.0.1.jar in your application's runtime. In order to activate code generation and generate implementations to manage your graph you will need to include dagger-compiler-2.0.1.jar in your build at compile time.
In a Maven project, include the dagger artifact in the dependencies section of your pom.xml and the dagger-compiler artifact as either an optional or provided dependency:
<dependencies> <dependency> <groupId>com.google.dagger</groupId> <artifactId>dagger</artifactId> <version>2.0.1</version> </dependency> <dependency> <groupId>com.google.dagger</groupId> <artifactId>dagger-compiler</artifactId> <version>2.0.1</version> <optional>true</optional> </dependency> </dependencies>
If you use the beta dagger-producers extension (which supplies parallelizable execution graphs), then add this to your maven configuration:
<dependencies> <dependency> <groupId>com.google.dagger</groupId> <artifactId>dagger-producers</artifactId> <version>2.0-beta</version> </dependency> </dependencies>
master branch on GitHub)If you do not use maven, gradle, ivy, or other build systems that consume maven-style binary artifacts, they can be downloaded directly via the Maven Central Repository.
Developer snapshots are available from Sonatype's snapshot repository, and are built on a clean build of the GitHub project's master branch.
Copyright 2012 Square, Inc. Copyright 2012 Google, Inc. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.