Upgrade java 8 to 1112/20/2023 ![]() ![]() Sun and Oracle have been telling developers for years not to use and other sharp-edge JDK APIs.įor a long time, Java 9 was to be the release where those classes disappeared. Consider using Getdown or Update4J instead. On the Java client side, things are more tricky with the removal of Java WebStart. However, if you use the Java EE modules then the fix for the deleted code should be simple in most cases. If you use Corba then there is little anyone can do to help you. These were parts of Java EE and Corba that no longer fitted well with the JDK, or could be maintained elsewhere. But in my opinion, you don't need to fully modularise to do this - just create a single jar-with-dependencies with a simple no-requires no-exports module-info.) (The main reason I've found to modularise your application is to be able to use jlink to shrink the size of the JDK. Right now, attempting to modularise is just painful as few dependencies are modules. ![]() Turning your application into Java modules may be a useful thing to consider in a few years time when open source dependencies really start to adopt modules. So my advice is to ignore modules as much as you can when upgrading to Java 11. This is terrible for library authors, but great for application developers. In most cases, code running on the classpath will continue to run on Java 9 and later where modules are completely ignored. You do not have to modularise your code to upgrade to Java 11. Much has been said on the topic, by me and others.Ī key point is sometimes forgotten however: Java 9 introduced one of the largest changes in the history of Java - modules. (And here are a couple of other blogs - Benjamin Winterberg and Leonardo Zanivan.) Here are a few of my notes on the process. Moving from Java 8 to Java 11 is trickier than most upgrades. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |