Take a look at the dependencies page for Commons Proxy: http://commons.apache.org/proxy/dependencies.html
Nothing is required other than the JDK. Now, this is a bit misleading. If you want to use any of the optional libraries (CGLIB and Javassist), then you of course have to include their dependencies. Commons Proxy manages its dependencies using Maven2, so it picks up whatever CGLIB and Javassist say they need. On Mon, Oct 20, 2008 at 10:42 AM, Brian Pontarelli <[EMAIL PROTECTED]> wrote: > > > I'm not a big fan of most of the commons libraries. They tend to pull > in a number of extra dependencies and most aren't JDK 5 converted yet. > Plus, this would only be useful if the CGLIB dependency was opened up > rather than pre-packaged. This commons library might be different, but > my guess is that it still depends on commons-lang, commons-logging and > maybe one more. I don't think that bundling CGLIB inside the JAR is a > bad thing personally. > > -bp > > > On Oct 16, 2008, at 11:42 PM, James Carman wrote: > >> >> Would the Google Guice project be interested in using Apache Commons >> Proxy (http://commons.apache.org/proxy/)? ACP basically allows you to >> create dynamic proxy objects using a standardized API without worrying >> about the underlying dynamic class library specifics. Right now, it >> includes support for JDK proxies, Javassist, and CGLIB (no ASM yet, >> but I imagine it could be done). >> >> > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
