From da8169c0319ec13ba19360064006b906371327af Mon Sep 17 00:00:00 2001
From: Stuart McCulloch <mcculls@gmail.com>
Date: Tue, 19 Mar 2013 01:12:21 +0000
Subject: [PATCH] Avoid mixing two flavours of Guice on the classpath.

Note: the main blocker to using Google-Guice for Maven3 is the lack of a release with the new ProvisionListener API, which is needed to support Plexus lifecycles. While there are other fixes/features in Sisu-Guice that are nice-to-have (such as removal of the big global singleton lock) they aren't strictly required for Maven3.
---
 maven-aether-provider/pom.xml | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/maven-aether-provider/pom.xml b/maven-aether-provider/pom.xml
index 926c51e2c36f..35daff114e76 100644
--- a/maven-aether-provider/pom.xml
+++ b/maven-aether-provider/pom.xml
@@ -88,9 +88,8 @@ under the License.
       <artifactId>plexus-utils</artifactId>
     </dependency>
     <dependency>
-      <groupId>com.google.inject</groupId>
-      <artifactId>guice</artifactId>
-      <version>3.0</version>
+      <groupId>org.sonatype.sisu</groupId>
+      <artifactId>sisu-guice</artifactId>
       <classifier>no_aop</classifier>
       <optional>true</optional>
       <exclusions>