3/4 of the industry? 75% ? you must be joking... do remember that 1.5 will not be released for quite some time so even in 2010 you have a 1.4 version for i think the whole year. So wicket 1.4 will only really be not so supported anymore in 2011 that means that java 5 will be more then 6 years old and java 6 will be on the market for more then 4 years..
even hardware is replaced before that .. we can try to avoid it for some time if possible, but if some stuff as nicer for the core then i am against a separate jar and ugly build system johan On Thu, Dec 24, 2009 at 15:47, Olivier Croisier <olivier.crois...@gmail.com>wrote: > Same here : > -1 to 1.6 dependencies in Wicket core. > +1 to additional 1.6-dependent features in separate jars. > > "Snow Leopard didn't install JDK 5 on my laptop" is not a valid excuse to > let down about 3/4 of the industry users, and neither is "it's free so they > cannot complain". > > Now, if some JDK6-only features are needed (Service Provider Interface, > webservices, etc.), a separate branch will be fine. Spring did it for years > with the Java 5 features. > > > On Thu, Dec 24, 2009 at 2:04 PM, elygre <eirik.ly...@gmail.com> wrote: > > > > > -1 to 1.6 dependencies in Wicket core. > > +1 to additional 1.6-dependent features in separate jars. > > > > Eirik > > -- > > View this message in context: > > > http://old.nabble.com/wicket-1.5-build-is-failing-because-of-1.6-deps...-tp26792764p26913700.html > > Sent from the Wicket - Dev mailing list archive at Nabble.com. > > > > >
