Why don't Guice and Warp simply depend upon an external cglib
library? My other dependencies use cglib so I am ending up with more and
more duplicates.
Gili
Dhanji R. Prasanna wrote:
>
>
> On Sat, Oct 11, 2008 at 5:32 AM, Gili Tzabari <[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>> wrote:
>
>
> Bob,
>
> There is one problem with "commit is the new version". Third-party
> tools such as Warp-* are built against Guice 1.0. Until you put out an
> official new version they will not bother updating their tools against
> it. I can (and have) used the trunk build of Guice but it's
> useless when
> it doesn't interoperate with my other dependencies...
>
>
> Yea, this is mostly my fault for binding to Guice's internals.
> Warp-persist 2.0 will repackage cglib under its own namespace at the
> cost of duplicate bytecode. This ought to break any hard dep on Guice 1.0.
>
> Note that warp-servlet has no such problems (and will be
> merged/superceded by guice-servlet 2.0 anyway).
>
> Dhanji.
>
> >
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
