See also https://groups.google.com/forum/?fromgroups#!topic/google-guice/Wz1XrRuX69U which talks a bit more about sisu-guice
So sisu-cglib was a temporary build-time-only artifact needed to get Guice 3.0 out the door (it isn't in trunk and it won't be in the next release) and sisu-guice is just an unofficial/experimental branch of Guice Neither artifact is actually needed to use Guice at compile or runtime with your application On 3 Aug 2012, at 16:41, Stuart McCulloch wrote: > On 3 Aug 2012, at 16:32, Wujek Srujek wrote: > >> Hi. I am evaluating Guice for my new project again, and I noticed that there >> are some sisu artifacts. Even the mmain maven repository has a guice 3 >> pom.xml with a reference to some sisu-cglib artifact (with a note that it >> should be replaced when official cglib comes out, which probably has >> happened already?). Could anybody shed some light on this? > > See > https://groups.google.com/forum/?fromgroups#!topic/google-guice/Rxk7d3SWFYE > for the full history > > Summary: it is a dependency of the build process, but is not required by > Guice at runtime because it is embedded (and relocated) inside > > If you look at the trunk build you will see that it now uses the latest > official CGLIB dependency that includes the fix needed by Guice > >> wujek -- You received this message because you are subscribed to the Google Groups "google-guice" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-guice?hl=en.
