From: Bill H. <bi...@lo...> - 2009-04-10 21:47:53
|
Hi Glen, The repackaging means that the Cglib is code has been moved into a different package, one under the proxool namespace. This means that if you use Cglib outside the Proxool code then you need both proxool-cglib.jar AND cglib-x.y.z.jar. The purpose of repackaging is to reduce the dependency on a particular version of Cglib. If you upgrade to Cgliv 2.whatever then Proxool won't be effected. - Bill 2009/4/10 Glen Peterson <gl...@or...> > Sorry to be dense, but I didn't understand what this meant in the > release notes for the latest version of proxool: > > "Fixed bundling of Cglib in binary release. Cglib is "repackaged" > using JarJar. This release just adds the file proxool-cglib.jar to the > binary release." > > Do I need to replace my cglib-2.3.1.jar with proxool-cglib.jar? Even > if I don't need to, should I? What did you change in cglib? > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > High Quality Requirements in a Collaborative Environment. > Download a free trial of Rational Requirements Composer Now! > http://p.sf.net/sfu/www-ibm-com > _______________________________________________ > Proxool-developer mailing list > Pro...@li... > https://lists.sourceforge.net/lists/listinfo/proxool-developer > |