nufasad.blogg.se - Compiling java with jdk 12

#Compiling java with jdk 12 update#
#Compiling java with jdk 12 upgrade#
#Compiling java with jdk 12 code#

Lots of things have changed since Java 8, and not just in terms of language features. Oracle started releasing two different builds, each with a different license (a commercial build which you need to pay to use in production and an open source OpenJDK build) and changed their update and support models.

Using a modern version of Java has an impact on the retention and recruitment of developers, which ultimately impacts the cost of running your team.

#Compiling java with jdk 12 upgrade#

There's always another potential benefit to consider in that using modern versions of a language also allows you to attract a wide range of developers, as many developers like to have the opportunity to learn new things and upgrade their skills. Not least of all tools like JLink reducing the size of the artifact we deploy, and recent improvements in memory usage could, for example, decrease our cloud computing costs. The improvements in recent versions of Java could lead to a cost reduction. Three might seem like overkill, but each collector optimises for different use cases, so now you have a choice of modern garbage collectors, one of which may have the profile that best suits your application. Java 9, 10, 11 and 12 all came with significant changes and improvements to Garbage Collection, including changing the default Garbage Collector to G1, improvements to G1, and three new experimental Garbage Collectors ( Epsilon and ZGC in Java 11, and Shenandoah in Java 12).

#Compiling java with jdk 12 code#

Generally speaking each new release performs better than the previous one. "Better" can take many forms, but in recent releases we've seen improvements in startup time reduction in memory usage and the use of specific CPU instructions resulting in code that uses fewer CPU cycles, among other things. JLink is a fantastic tool made possible by the Java Module System which lets us package and deploy only the sections of the JDK that we really need. Multi release jar files is one of the tools library developers can use to support the needs of those using the latest versions of Java as well as those forced to use older versions. The built in client removes the need for external dependencies, and supports HTTP 1.1 and 2 with both synchronous and asynchronous programming models. Almost everyone is working with HTTP in some form or other, via web applications or REST services or something else.

It’s a nice way to experiment with new features, and we can use it locally on our development machines without having to adopt new versions of Java in our production application code.Īn HttpClient built in to the JDK. JShell is the REPL that allows us to run individual lines of code, or even scripts, in Java. New methods on Optional give even more options for coding in a functional style when using an Optional instead of having to use clumsy ifstatements. Predicate::not provides an easy way to negate predicate lambdas or method references, again reducing the boilerplate in our code.

Once "over the hump" of this first upgrade, it's worth at least testing the application on the latest version of Java every 6 months, for example in CI.Ĭollecting to unmodifiable collections is possible using the new Collector for Streams operations to put the results into an immutable collection.

These changes may impact your application but there is a clear path to avoid these problems. APIs that are not core to the JDK have also been removed in Java 11.

One of the changes from Java 9 was that internal APIs (largely those classes in packages that started with sun.misc.*) were hidden from use.

Deprecation is being taken much more seriously in this modern Java world, and both Java 10 and Java 11 removed APIs.

Don’t be tempted to ignore compiler warnings.

When choosing to upgrade the choice you face is whether to upgrade to the latest version of Java (12) and be prepared to upgrade every six months or upgrade to the latest LTS (11) to give yourself up to three years to think about your next upgrade.

Since Java 8 a number of useful new language features have been introduced, along with new tooling, and performance improvements particularly for garbage collection.