On Fri, Mar 27, 2009 at 11:08 AM, Werner Punz <[email protected]> wrote: > Matthias Wessendorf schrieb: >> >> On Fri, Mar 27, 2009 at 10:49 AM, Werner Punz <[email protected]> >> wrote: >>> >>> Well I can live with it although I dont see too much reason to target >>> java6 >>> codewise, since we do not use too many new features of it extensively >>> (In january it was just one data structure which replaced the old Stack >>> data >>> structure that was it). >>> >>> I think we should target java5 still in our core codebase to allow the >>> integration into jee5 based servlet runners. >>> Although JEE6 will come out in summer probably, JEE5 will be the defacto >> >> they changed that date to September.. >> >>> base for the years to come, since the migration from jee4 to jee5 happens >>> as >>> we speak by now! >> >> I doubt that much vendors will add additional support for JSF 2 in >> their existing >> JavaEE 5 environments >> > Well a not totally unimportant userbase is the one, who integrates the jsf > core into tomcat or other servlet runners. > Some of them if not many of them will be stuck on JDK5 for political > reasons. :-) > > As much as I love to target the latest technology, I think for a core > framework we should be a tad more conservative, but as I said that > is just my 2c regarding the entire situation. Especially since targetting > JDK5 does not induce pain like it did with JDK4 when everyone finally wanted > to get up to JDK5 for various reasons regarding the language extensions :-)
yes, I know. I have never that I want to have JSE 6, I just want to reflect the spec requirements correctly. Let me ping the folks on the RI dev-list for that type of q. -M > > As I said just a personal opinion, nothing more! > > > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
