forked from roboguice/roboguice
-
Notifications
You must be signed in to change notification settings - Fork 0
InstallationMaven
emmby edited this page Dec 3, 2012
·
3 revisions
Install RoboGuice for Projects Using Maven
Add the following pom to your <dependencies>
list in your pom.xml:
<dependency>
<groupId>org.roboguice</groupId>
<artifactId>roboguice</artifactId>
<version>2.0</version>
</dependency>
If you'd like to be able to mark certain injections as Nullable, you'll want to add the optional @Nullable annotation as well. You may not use this, but if you'd like to:
<!-- For the optional Nullable annotation -->
<dependency>
<groupId>com.google.code.findbugs</groupId>
<artifactId>jsr305</artifactId>
<version>1.3.9</version>
</dependency>
- For Projects Using Maven
- For Non-Maven Projects
- Inheriting from RoboGuice Classes
- (Upgrade Instructions for Users of RoboGuice 1.1)
- Your First View Injection
- Your First Resource Injection
- Your First System Service Injection
- Your First POJO Injection
- Your First Singleton and ContextSingleton (wiki/Understanding Scopes)
- Your First Custom Binding
- Your First Injected Fragment
- Your First Injected Service and BroadcastReceiver
- Your First Testcase
- Your First Injection into a Custom View class
- Your First Injected Content Provider
- How Injection Works
- When Injection Just Works, and when you have to call injectMembers()
- The Difference between Global and Context-scoped Injection
- Analyzing a Guice Stack Trace
- What's the difference between Nullable and Optional?
- Remove or replace RoboGuice's default bindings
- Use your own BaseActivity with RoboGuice
- Inject into an object that you don't instantiate
- Dealing with Circular Dependencies
- Work with Library Projects
- Deal with ComputationException due to StackOverflowError
- Taming Fragmentation using RoboGuice