-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Thanks for the feedback, all done.
|I notice that in the binary distribution, the "lib" directory has a copy
|of all the jelly dependencies already.
|
|This is unusual for commons, but then I guess no other commons project
|is meant to be "runnable out of the box".
right...
|
|However I do notice that all these bundled libs are very old. Are these
|libs the dependencies as listed in the project.xml? Those entries will
|of course be the *oldest* versions that are compatible with jelly. When
|distributing Jelly, however, it might be a good idea to provide the
|*latest* jars rather than the *oldest* jars. On the other hand, that
|means providing jars that the unit tests weren't run with so maybe not.
|Worth thinking about anyway...
yes, I'm not comfortable distributing newer libraries than have been
tested against. I'll get back to implementing dependency version
management in Maven2 once this is done so we can start solving that
problem :)
- - Brett
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCq6FxOb5RoQhMkRMRArLUAKC5RCPQswaYykHN116/CAvoqLlIyACfWD5i
7cxa1Y+VJuauSZddJJvbDxo=
=Utbu
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
