Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


David,

Yes! I will happily work with your JDK 7 based build with Java 7 bytecode to
see if that restores the JAB function Oracle clobbered when they moved Java
Access Bridge into the base JRE at 1.7u6.

Thanks for the history...

Can't fault Tor's work on fixing the compiler java_target_version to 1.5
across all build platforms.

But the comments made in rejecting your
https://gerrit.libreoffice.org/#/c/2884/  seem a little short sighted
because at that point we'd already demonstrated that the JRE 7 built in JAB
was NOT functioning correctly for providing UAA based Assistive Technology
tools to Windows OS desktops and filed fdo#58995. 

And any of the thousands of AT dependent LibreOffice users on Windows can
attest that UAA <--> JAB AT is  impacted because we've had to have folks
jump through hoops to obtain a functional AT  (see  
https://wiki.documentfoundation.org/Faq/Java  or 
https://wiki.documentfoundation.org/Accessibility ).

Issue of bytecode target interaction with JRE becomes more troubling if you
consider that the default Java JRE update settings on Windows systems
replace all JRE  6 installations with current JRE 7 builds.  In other words
the percentage of total LibreOffice ussers with JRE 1.5 or JRE 1.6
installations even installed is rapidly shrinking.  

Stuart



--
View this message in context: 
http://nabble.documentfoundation.org/Question-on-Java-JDK-build-environments-impacting-JRE-use-tp4062592p4062733.html
Sent from the Dev mailing list archive at Nabble.com.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.