IMO, we should definetly go with JDK1.5 for next major Tapestry release.
Also, I don't want to sound pesimistic, but looking at Tapestry's release
pace till now, I somehow doubt that this release will be final when
initially thought, so let's assume it won't be final in Q3 2006, but in the
beginning of 2007.
So, does someone object with using JDK1.5 in 2007 (!!!) ?
This reminds me with discussion about being JDK1.4 dependant for Tapestry
4.0... As we see it now, 4.0 is going final in the beginning of 2006, and
not beginning of 2005 or whenever initial talks were about. So, now it looks
a bit silly for me to be in 2006 and worry about JDK1.3. I realize there is
small number of people that still have to stick with 1.3, but hey, they can
use 3.0.3 then .... *large* majority think about 1.3 as stone-age. I think
we should think about JDK1.5 along the same lines. Of course, it wasn't such
a impact with JDK1.3-compatibility because there wasn't some major tradeoff
compared with JDK1.4, so I guess back-compatibility could be justified, but
JDK1.5 is another beast.
Also, looking at harsh competition in web framework area, Tapestry will have
to offer latest and greatest of web development if wanting to prevail, and
knowing that it has most garbage dragging along since it is the oldest of
currently popular (JSF, Wicket, Spring MVC, WebWork...), worrying too much
about back-compatibility can be major obstacle...
-Vjeran
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
