 |
 |
When you have them installed side-by-side, Java 1.7 will be invoked by default but it is pretty trivial from my understanding to make your jar file request older, non-default JRE installs which means once March comes around having that old install hanging around will become an increasing liability. On Tue, 5 Feb 2013 13:59:15 -0500, Carl Bussema III <[log in to unmask]> wrote: >SqlDeveloper 3.2 (released November 2012), which is the recommended way to >connect to the EBS Data Warehouse, runs on Java 1.6.x. It sort of runs on >1.7, but it's officiallly Not Supported (TM) and produces a Big Nasty >Warning and has some odd quirks. The consensus is that depending on what >features of it you're using, you may or may not be able to live with 1.7. >AFAIK, no official plans have been announced for Oracle to update this >software to run with Java 1.7. > >That said, it's perfectly happy using Java 1.6 while Java 1.7 is installed >and is the default, so I'm not sure what that does for your security >vulnerability. > >Carl Bussema III >Information Technologist >Michigan State University Outreach & Engagement >Phone: (517) 353-8977 • Fax: (517) 432-9541 >[log in to unmask]