In the end, I think staying on long term support versions or using the latest version shouldn't differ too much in the investment that needs to be done in upgrading. However, then, each time you need to upgrade your long term support version, that actually might take quite a bit more time as well. If you don't have that time available to upgrade every six months, you might opt to using only the long term support versions. You have to do it every six months, because you cannot use the new minor versions. However, because it's a major version, it might take a bit more work. Should we then stick to using LTS versions, or should we use the latest versions of Java? If you have the time available, I would recommend using the latest version of Java because you can use the new features, there's new things, and also increase developer productivity. It also has minor updates, but only until the next major release is created. Between those LTS versions, we also have the six monthly Java releases. Depending on the vendor that created your build, it can be for a much longer period, but that differs per vendor. The major LTS versions also receive minor updates, and those updates are at least until the next LTS version is released. The next one will be 17, which will be released in September this year. Releasesįor Java, nowadays, we have the long term support or LTS versions, which are released every couple of years. Therefore, I use Maven as an example but of course this works with Gradle as well or any other build tool that you prefer. I will share some recurring challenges and their solutions that I've discovered over the years with various Java versions, to help you get the migration to the newest version of Java in a quick manner. Depending on what dependencies you use, or what code bases you use, it might be a bit more of a challenge. It's often a matter of simply trying it, and if you're lucky, you manage to upgrade it quite easily. Of course I had some prior experience with the Java Upgrades. Actually, in the case of the weeks to months' estimation, I managed to do it in a couple of days. Then, when that information is being sent to the business, they often say, we don't have time to invest so much time now. It's often estimated that it's a lot of work, maybe even weeks or months of work to upgrade from one LTS version to the next LTS version of Java, the long term support versions. I've noticed that a lot of applications are still on Java 8 or maybe even older, because upgrading is seen as quite a challenge. It includes cool, new features, for instance, the recently released Java records or the pattern matching functionality. Why should you actually upgrade your application? Every Java version, even minor versions offer performance benefits, but also security fixes and other useful extras that make your application more robust and better maintainable. ![]() I've been doing that for quite a while for bigger applications with hundreds of thousands of users a day. ![]() That was during the process of upgrading many applications over the years to newer Java versions. I didn't get this information by upgrading HelloWorld or by Googling a lot. A lot of the things in this presentation are based on that repository, which includes examples and a lot of information on challenges that you encounter, errors that you might see, and the solutions for that. If you have any questions, please have a look at the GitHub repository, Java Upgrades, which I created. ![]() Then see what the challenges are of the various Java versions and how we can resolve them. Then we start with the more practical parts on how you should actually upgrade your Java application, and some tips and tricks for that. Then we have a look at the release cadence of Java. What are we going to talk about? First, we start with the reasons on why you should actually upgrade your application to the newest version of Java.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |