[sakai2-tcc] 2.6.3 and Java 6

[Matthew Jones]

I partially agree, but Java 5 has been end of life for over 8 months (as of
today) and isn't *easily* available the latest OSX release. So these would
be the biggest reasons, security fixes and easier availability, to recommend
using a new version even on a minor, even if though need to use options.

However it should remain compilable with Java 5, at least until 2.8. (No new
language features allowed)

I'd be interested in how many QA's and production instances are on Java 6.
Currently University of Michigan is still running Sakai 2.6 on Java 5
because of some unresolved load test issues with Java 6. We hope to revisit
these soon and ideally will be on Java 6 in the next few months.

On Wed, Jul 21, 2010 at 11:10 AM, csev <csev at umich.edu> wrote:

> It would seem strange to change the JVM version in a minor release unless
> there is some strong issue.
>
> If 2.6.0 recommended Java 1.5 - then absent some overriding concern, 2.6.3
> should recommend 1.5 as well.
>
> /Chuck
>
> On Jul 21, 2010, at 7:32 AM, Anthony Whyte wrote:
>
> > Shall we recommend deployers run 2.6.3 in a Java 6 SE JVM?  If so, I'll
> update the demo start up script in 2.6.x as well as the release notes.
> >
> > Cheers,
> >
> > Anth
> >
> >
> > _______________________________________________
> > sakai2-tcc mailing list
> > sakai2-tcc at collab.sakaiproject.org
> > http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>
> _______________________________________________
> sakai2-tcc mailing list
> sakai2-tcc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20100721/ee5abc5f/attachment.html