We have been using commons-lang-2.0 with Tapestry 3.0.x for quite sometime now, including 3 production sites with about 100 users.
To validate that using commons-lang-2.0 was possible, I found all the references to commons-lang classes and assured myself I was not creating trouble for myself. I would suggest that you do a similar exercise as YMMV. Richard -----Original Message----- From: Greg Ward [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 31, 2005 8:38 AM To: [email protected] Subject: Any problems with Tapestry 3 and commons-lang 2.1? I'd like to use commons-lang 2.1 with my app -- but Tapestry 3.0.3 ships with 1.0. Is there any particular reason why Tapestry 3 includes commons-lang 1.0, or is it just that that was the current version when Tapestry 3 came out? I'm running my app with commons-lang 2.1 right now, and everything seems fine ... but if I'm going to be bitten by some obscure corner of Tapestry that depends on some obscure corner of commons-lang 1.0, I'd like to know ahead of time. Thanks -- Greg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
