Howard and Patrick, I stand corrected. I assumed that 4.0 would be kind of an unfinished version that would have most bugs polished in 4.1. It is now clear that version 4.0 will be JDK1.4 compatible and TP 4.1 might not.
I liked MindBridge's proposal a lot. Does it mean that all 4.1 releases would need to be tested against retroweaver by the dev team? Regards, Dario On 12/20/05, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > On 12/20/05, Darío Vasconcelos <[EMAIL PROTECTED]> wrote: > > I'm just a small-time development shop in a third-world country, but > > in my current work environment (Oracle IAS and WAS 5 mostly, some > > Tomcats) it will take ages for my customers to upgrade to JDK 1.4 > > -capable app servers. Except for the Tomcat installations, they're > > still on 1.3... > > > > This would mean for me no TP4, and though I'm perfectly happy with > > 3.0.3, there are plenty of improvements in version 4 that I would be > > missing. Now, is the latest 4.0.x version stable enough for > > production? I've been following the list closely but it's a little bit > > difficult to evaluate how buggy it **really** is... > > To be clear: This dicussion is about the NEXT release of Tapestry > (4.1), not the current release (4.0) which will hopefully be final by > the end of this month (or early January 2006). > > > > > > -- > 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] > > -- "Painting: The art of protecting flat surfaces from the weather and exposing them to the critic." Ambrose Bierce --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
