Yes and no. We lose backwards compatibility either way, and the commons-lang stuff isn't that necessary ... and fewer dependencies is always better in the long run. Common libraries like commons-lang are great for application developers but ultimately cause problems for framework developers due to dependency hell (framework A relies on commons-lang 2.0, framework B relies on commons-lang 2.1 ... that kind of thing).
On 6/14/05, Matt Doran <[EMAIL PROTECTED]> wrote: > All, > > I was just reviewing the Tapestry 4 upgrade guide an noticed that the > common-lang dependency was removed, due to JDK 1.5 compliance > problems. > > We are also using commons-lang and had this problem, but they've > *just* released 2.1 which fixes this issue. > (http://www.apache.org/dist/jakarta/commons/lang/RELEASE-NOTES.txt) > > They've deprecated the "enum" package and renamed it to "enums", which > fixes the JDK 1.5 compliance. > > Not a big deal, but I guess you could keep support for commons lang Enum now. > > Cheers, > Matt Doran > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
