Re: Ready for JDK 9 ?
Hello Muneer, I have created incident 9050418 for point 2. Best regards, Vincent 2017-08-08 13:03 GMT+02:00 Muneer Kolarkunnu : > Hi Vincent, > > > > Regarding the points in the below email: > > (2) Can you please raise an incident for this? > > (3) I added josm-interest label on JDK-8058778 and we let you know once it > get fixed. > > > > Regards, > > Muneer > > > > *From:* Rory O'Donnell > *Sent:* Tuesday, August 08, 2017 3:53 PM > *To:* Vincent Privat > *Cc:* Rory O'Donnell; Dalibor Topic; Balchandra Vaidya; Muneer > Kolarkunnu; josm-dev > *Subject:* Re: Ready for JDK 9 ? > > > > Great news, thanks for the update! > > Rgds,Rory > > > > On 08/08/2017 10:59, Vincent Privat wrote: > > Hello Rory, > > Just in time ! We announced the JDK9 full compatibility less than 2 days > ago: > > https://josm.openstreetmap.de/ticket/11924 > > > > The compatibility effort was significant, but shared with the whole Java > ecosystem (as we created bug reports to Ant, Groovy, EqualsVerifier, > Geotools, FindBugs/SpotBugs, ErrorProne, etc.). > > > > Aside Jigsaw, the three JDK9 changes that impacted us most were: > > 1) The Math improvements to Math.cos in b105 (JDK-8143353, see > https://josm.openstreetmap.de/ticket/11889 + https://josm.openstreetmap. > de/ticket/13387). It took us a long time to spot why > > our floating point calculations changed in JDK9. But we noticed a huge > performance gain, and more accurate results too. This is a huge > improvement, thanks! > > 2) The deprecation of _MASK constants in favor of _DOWN_MASK constants > (JDK-8143077). It was not easy to switch because ActionEvent does not > provide extended modifiers (there's no getModifiersEx() method in this > class. I think it should have been added in 9, could you please consider it > in 10 ?). > > 3) The impossibility to disable the "proprietary API warning" in 9 (we > disabled it with non-supported option -XDignore.symbol.file in 8). Until we > switch our codebase to a version of Java providing the new certificate > creation API (JDK-8058778), we must keep our current implementation based > on sun.x509 packages. Currently the best I can do is tell our Jenkins > instance to filter this warning. > > > > Congrats for this major release of Java, > > Best regards, > > Vincent > > > > > > > > 2017-08-08 11:30 GMT+02:00 Rory O'Donnell : > > > Hi Vincent, > > Thank you very much for all your testing of JDK 9 during its development! > Such contributions have significantly helped shape and improve JDK 9. > > Now that we have reached the JDK 9 Final Release Candidate phase [1] , I > would like to ask if your project can be considered to be 'ready for JDK > 9', or if there are any remaining show stopper issues which you've > encountered when testing with the JDK 9 release candidate. > > JDK 9 b181 is available at http://jdk.java.net/9/ > > If you have a public web page, mailing list post, or even a tweet > announcing you project's readiness for JDK 9, I'd love to add the URL to > the upcoming JDK 9 readiness page on the Quality Outreach wiki. > > > Looking forward to hearing from you, > Rory > > [1] http://openjdk.java.net/projects/jdk9/ > > -- > Rgds,Rory O'Donnell > Quality Engineering Manager > Oracle EMEA , Dublin, Ireland > > > > > > -- > > Rgds,Rory O'Donnell > > Quality Engineering Manager > > Oracle EMEA , Dublin, Ireland > >
Re: Ready for JDK 9 ?
Great news, thanks for the update! Rgds,Rory On 08/08/2017 10:59, Vincent Privat wrote: Hello Rory, Just in time ! We announced the JDK9 full compatibility less than 2 days ago: https://josm.openstreetmap.de/ticket/11924 The compatibility effort was significant, but shared with the whole Java ecosystem (as we created bug reports to Ant, Groovy, EqualsVerifier, Geotools, FindBugs/SpotBugs, ErrorProne, etc.). Aside Jigsaw, the three JDK9 changes that impacted us most were: 1) The Math improvements to Math.cos in b105 (JDK-8143353, see https://josm.openstreetmap.de/ticket/11889 + https://josm.openstreetmap.de/ticket/13387). It took us a long time to spot why our floating point calculations changed in JDK9. But we noticed a huge performance gain, and more accurate results too. This is a huge improvement, thanks! 2) The deprecation of _MASK constants in favor of _DOWN_MASK constants (JDK-8143077). It was not easy to switch because ActionEvent does not provide extended modifiers (there's no getModifiersEx() method in this class. I think it should have been added in 9, could you please consider it in 10 ?). 3) The impossibility to disable the "proprietary API warning" in 9 (we disabled it with non-supported option -XDignore.symbol.file in 8). Until we switch our codebase to a version of Java providing the new certificate creation API (JDK-8058778), we must keep our current implementation based on sun.x509 packages. Currently the best I can do is tell our Jenkins instance to filter this warning. Congrats for this major release of Java, Best regards, Vincent 2017-08-08 11:30 GMT+02:00 Rory O'Donnell <mailto:rory.odonn...@oracle.com>>: Hi Vincent, Thank you very much for all your testing of JDK 9 during its development! Such contributions have significantly helped shape and improve JDK 9. Now that we have reached the JDK 9 Final Release Candidate phase [1] , I would like to ask if your project can be considered to be 'ready for JDK 9', or if there are any remaining show stopper issues which you've encountered when testing with the JDK 9 release candidate. JDK 9 b181 is available at http://jdk.java.net/9/ If you have a public web page, mailing list post, or even a tweet announcing you project's readiness for JDK 9, I'd love to add the URL to the upcoming JDK 9 readiness page on the Quality Outreach wiki. Looking forward to hearing from you, Rory [1] http://openjdk.java.net/projects/jdk9/ <http://openjdk.java.net/projects/jdk9/> -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland
Re: Ready for JDK 9 ?
Hello Rory, Just in time ! We announced the JDK9 full compatibility less than 2 days ago: https://josm.openstreetmap.de/ticket/11924 The compatibility effort was significant, but shared with the whole Java ecosystem (as we created bug reports to Ant, Groovy, EqualsVerifier, Geotools, FindBugs/SpotBugs, ErrorProne, etc.). Aside Jigsaw, the three JDK9 changes that impacted us most were: 1) The Math improvements to Math.cos in b105 (JDK-8143353, see https://josm.openstreetmap.de/ticket/11889 + https://josm.openstreetmap.de/ticket/13387). It took us a long time to spot why our floating point calculations changed in JDK9. But we noticed a huge performance gain, and more accurate results too. This is a huge improvement, thanks! 2) The deprecation of _MASK constants in favor of _DOWN_MASK constants (JDK-8143077). It was not easy to switch because ActionEvent does not provide extended modifiers (there's no getModifiersEx() method in this class. I think it should have been added in 9, could you please consider it in 10 ?). 3) The impossibility to disable the "proprietary API warning" in 9 (we disabled it with non-supported option -XDignore.symbol.file in 8). Until we switch our codebase to a version of Java providing the new certificate creation API (JDK-8058778), we must keep our current implementation based on sun.x509 packages. Currently the best I can do is tell our Jenkins instance to filter this warning. Congrats for this major release of Java, Best regards, Vincent 2017-08-08 11:30 GMT+02:00 Rory O'Donnell : > > Hi Vincent, > > Thank you very much for all your testing of JDK 9 during its development! > Such contributions have significantly helped shape and improve JDK 9. > > Now that we have reached the JDK 9 Final Release Candidate phase [1] , I > would like to ask if your project can be considered to be 'ready for JDK > 9', or if there are any remaining show stopper issues which you've > encountered when testing with the JDK 9 release candidate. > > JDK 9 b181 is available at http://jdk.java.net/9/ > > If you have a public web page, mailing list post, or even a tweet > announcing you project's readiness for JDK 9, I'd love to add the URL to > the upcoming JDK 9 readiness page on the Quality Outreach wiki. > > > Looking forward to hearing from you, > Rory > > [1] http://openjdk.java.net/projects/jdk9/ > > -- > Rgds,Rory O'Donnell > Quality Engineering Manager > Oracle EMEA , Dublin, Ireland > >
Ready for JDK 9 ?
Hi Vincent, Thank you very much for all your testing of JDK 9 during its development! Such contributions have significantly helped shape and improve JDK 9. Now that we have reached the JDK 9 Final Release Candidate phase [1] , I would like to ask if your project can be considered to be 'ready for JDK 9', or if there are any remaining show stopper issues which you've encountered when testing with the JDK 9 release candidate. JDK 9 b181 is available at http://jdk.java.net/9/ If you have a public web page, mailing list post, or even a tweet announcing you project's readiness for JDK 9, I'd love to add the URL to the upcoming JDK 9 readiness page on the Quality Outreach wiki. Looking forward to hearing from you, Rory [1] http://openjdk.java.net/projects/jdk9/ -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland