-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hensley, Richard wrote: | JDK 5 has already been advanced as the build tool for Hivemind. I don't | think the same requirement for Tapestry 4.0 is a bad thing. | | Richard |
'been advanced' is not the same in this situation as 'been decided'. That aside, I do not believe that the view of "Tapestry Developer == Hivemind Developer" is, or should be, necessarily accurate. As long as the binary is used by Tapestry, then source compilation of Tapestry should stand on its own. I'm a +1 personally to going to 1.5, but -0 for Tapestry as a project going to 1.5 at the current time. Perhaps I'm being overly cautious, but I've read too much about developers not being able to move on to 1.5 yet (customers/corporate decisions/platforms/etc). Whether this holds any sway in their need to compile Tapestry, however, is a separate matter altogether. Brian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) iD8DBQFCp46taCoPKRow/gARAp9DAKCqXDs75oEK+u0j++nvvz0p2W0TGACgwTjL vfEfRhdUxPzd2N2jqkIRD14= =BXsk -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
