3 ms·

Java actually removes deprecated APIs now, and it's doing it really really quickly (IMHO way too fast). For example javax.activation, javax.activity, javax.rmi

Java actually removes deprecated APIs now, and it's doing it really really quickly (IMHO way too fast). For example javax.activation, javax.activity, javax.rmi, javax.transaction, javax.xml.bind, javax.xml.ws, javax.jws, and javax.xml were deprecated in Java 9 (released September 2017) and removed in Java 11 (released September 2018). JavaFX was deprecated in Java 10 and removed 6 months later in Java 11. Dealing with Java 11 was really painful to the point where it really feels like Python 3 of Java. The company I work for had less issues with migrating to Python 3 than with migrating to Java 11, but your mileage may vary.

shock 7y ago
> JavaFX was deprecated in Java 10 and removed 6 months later in Java 11 JavaFX is not deprecated. JavaFX was extracted from the JDK as a standalone project: https://openjfx.io/ https://openjfx.io/
- snuxoll 7y ago
  Ditto with the the other Java EE API’s GP mentioned, their interfaces are available on Maven Central instead of being bundled in the JDK - which makes sense as Java EE is not actually a thing anymore and the Eclipse Foundation took over as Shepard.
  - cesarb 7y ago
    > Ditto with the the other Java EE API’s GP mentioned, their interfaces are available on Maven Central Not all of them; AFAIK, there's no Maven Central artifact for what used to be in the CORBA packages.
    - pjmlp 7y ago
      Here you go, https://mvnrepository.com/artifact/com.sun.corba https://mvnrepository.com/artifact/com.sun.corba
imtringued 7y ago
They are no longer included by default but you can still add them back as maven/gradle dependencies.