We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Challenges updating your code to work with Java 9 Jigsaw

Formal Metadata

Title
Challenges updating your code to work with Java 9 Jigsaw
Title of Series
Number of Parts
611
Author
License
CC Attribution 2.0 Belgium:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language
Production Year2017

Content Metadata

Subject Area
Genre
Abstract
With the introduction of the Jigsaw module system many projects are confrontedwith issues running their code, now throwing new Exceptions likeInaccessibleObjectException because they used to work around issues in theJava API. Although many features like the famous sun.misc.Unsafe are nowprovided by other public APIs, there is still the problem of making your codework with previous Java versions, but also dynamically using the new Java 9replacements. Apache Lucene, the open source fulltext search library behindApache Solr and Elasticsearch, is also using some of those "hacks" to workaround issues in the Java API, but the developers also noticed that some codein the project hit some limits introduced by the module system. This talk willshow on some examples how Apache Lucene managed to allow its code to run withdifferent java versions (without using multi-release JAR files, as this bringsadditional burden with the build system) and still offer backwardscompatibility to earlier versions. It will show also the common pitfalls thatcan be easily found with running your tests in a security manager to uncoverbugs.