If the only reason we're moving to 1.6 is to support a newer version of hibernate in tapestry-hibernate, then I'm -1. I specifically know of a corporation out there using tapestry that still uses java 1.5. Where there's one, there are many. I suppose we could write them off as "stuck on tapestry 5.3.x", but unless there's some major benefit to switching to 1.6... why limit your potential customer base?
While we're on the topic, I'm not particularly keen on tapestry-hibernate attempting to force a particular hibernate version. I would much rather see the hibernate dependency declared as "provided" (in maven parlance) and specify a version range of compatible versions. Robert On May 2, 2012, at 5/21:05 AM , Kalle Korhonen wrote: > When in doubt, let's ask the community: would you object to requiring > JRE 1.6 for running Tapestry 5.4? So far, T5 has run on JRE 1.5 but > the time for requiring 1.6 will come at some point. Not necessarily > yet - we can likely work around this - but current Hibernate 4.x > releases are built with 1.6. > > Kalle > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
