[evla-sw-discuss] Java 7 on EVLA

[Bryan Butler]

right, but i'd bet a good chunk of our users are using chrome on a mac...

       -bryan

Sent from my iPhone.


On Oct 24, 2012, at 13:15, Keith Cummings <kcumming at nrao.edu> wrote:

> FYI, this is only true for Chrome running on a MAC because that Chrome version, by default, is only 32-bit.
> 
> Bryan Butler wrote:
>> 
>> one side note that we should consider - i believe chrome doesn't currently support java 7. at least that's the message i got when i went to download it last week. 
>> 
>>        -bryan
>> 
>> Sent from my iPhone.
>> 
>> 
>> On Oct 24, 2012, at 12:09, James Robnett <jrobnett at nrao.edu> wrote:
>> 
>>   
>>> Marie has not been running around 'scaring' you into an upgrade.
>>> 
>>> We have to upgrade java to Java 7 due to some very real and
>>> actively exploited security vulnerabilities in Java.
>>> 
>>> We have bent over backwards to set up tests and help see to what
>>> extent EVLA software will be affected.  We have never and never
>>> will impact EVLA operations even for something as serious as this,
>>> on the other hand EVLA software can't assume the world outside
>>> is frozen,  a calculated risk was accepted in using something
>>> like JAVA,  the benefit is high level language, the downside is
>>> moving target.
>>> 
>>> Figure out what you're doing and let us know.
>>> 
>>> James (who's growing weary of this)
>>> 
>>> 
>>> On 10/24/2012 01:01 PM, Daniel Lyons wrote:
>>>     
>>>> On 10/24/2012 12:53 PM, Bryan Butler wrote:
>>>>       
>>>>> not quite sure what you mean by "the EVLA will be switching to Java 7
>>>>> soon," kevin?
>>>>> 
>>>>> we've talked about some applications moving to it, but had no (formal)
>>>>> discussion of mandating that all of them have to...
>>>>>         
>>>> Marie has been going around scaring us into testing our stuff under Java
>>>> 7 in anticipation of a very near-term upgrade. There are security issues
>>>> with Java 6, which is reaching end-of-life in February, and it is
>>>> desired (by whom I'm not sure) that we sidestep the backporting delay
>>>> this way.
>>>>       
>>> _______________________________________________
>>> evla-sw-discuss mailing list
>>> evla-sw-discuss at listmgr.cv.nrao.edu
>>> http://listmgr.cv.nrao.edu/mailman/listinfo/evla-sw-discuss
>> 
>> _______________________________________________
>> evla-sw-discuss mailing list
>> evla-sw-discuss at listmgr.cv.nrao.edu
>> http://listmgr.cv.nrao.edu/mailman/listinfo/evla-sw-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listmgr.nrao.edu/pipermail/evla-sw-discuss/attachments/20121024/5768363b/attachment.html>