I'm loving google-collections - its a great piece of work. guice currently hides this dependency (and cglib) - including this code inside the guice jar via jarjar.
Now this is a good idea while google-collections is in a state of flux and not locked down at the 1.0 release, so that projects can use different google-collections versions without fear of breaking guice etc. However for folks who also want to use google-collections (or to use guice to encourage folks to use it :) then it doesn't always make heaps of sense hiding it. I wonder whenever we have the maven build patches applied, should we have have different artifacts; the 'jarjar'd version' with cglib/google-collections all inside guice - plus a separate jar which depends on the real cglib and google-collections jars - then folks can choose whether or not they want the jarjar'd version or the not? e.g. in maven-land you could depend on the artifactId guice-all-complete.jar or guice-all.jar (say) with the former including cglib/google-collections internally jar-jar'd and the latter just having more pom.xml dependencies? -- James ------- http://macstrac.blogspot.com/ Open Source Integration http://open.iona.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
