You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@tapestry.apache.org by Greg Ward <gw...@python.net> on 2005/08/31 17:37:40 UTC

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: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org