On 05.05.2017 08:39, Jeremy Manson wrote:
Mostly, I'm telling you all because I think it makes an interesting case study - a large Java installation and the issues it faces trying to roll out JDK 9.
Indeed - thank you for providing valuable insight into your concerns and experiences.
If other installations do the kinds of things that we do, the path to a JDK 9 without lots of add-exports and kill switch options is likely to be slow and laborious for them. We're comparatively well situated to do it - we have our own JDK build and a staffed team to do / help with the migration, and are likely to roll it out to everyone with the kill switch turned on by default so that our awful hacks can stay put until we finish fixing them.
I think part of responsibly relying on awful hacks leveraging unsupported behavior is to budget for their removal/rewrite as the assumptions behind them get invalidated over time.
Sometimes, it might be well known where the awful hacks are buried, in particular with one's own code. Other times, in particular with third party code, it might not be quite as obvious. That's where the jdeps & jdeprscan tools come in to help get a sense of the scope & intensity of such problems at compile time.
The kill switch complements that at runtime. cheers, dalibor topic -- <http://www.oracle.com> Dalibor Topic | Principal Product Manager Phone: +494089091214 <tel:+494089091214> | Mobile: +491737185961 <tel:+491737185961> ORACLE Deutschland B.V. & Co. KG | Kühnehöfe 5 | 22761 Hamburg ORACLE Deutschland B.V. & Co. KG Hauptverwaltung: Riesstr. 25, D-80992 München Registergericht: Amtsgericht München, HRA 95603 Komplementärin: ORACLE Deutschland Verwaltung B.V. Hertogswetering 163/167, 3543 AS Utrecht, Niederlande Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697 Geschäftsführer: Alexander van der Ven, Jan Schultheiss, Val Maher <http://www.oracle.com/commitment> Oracle is committed to developing practices and products that help protect the environment
