Promoting the answer in the comments to an answer, because it’s the actual answer: This appears to be a bug in the IntelliJ Kotlin plugin v1.2.40 and how it interacts with Java 10. See here. The solution is to upgrade to v1.2.41. (Don’t switch your project to building with Gradle like the other answer suggests … Read more
I made this answer a while ago where I answered this as an additional info to exposing non java.se packages in Java-9 using Maven. The added part specifically focusses on using the standalone version of the java.xml.* APIs. To adapt to which you can probably start consuming the dependency on jaxb-api:2.3.0 which can be loaded … Read more
The reason behind this is that meanwhile creating your own class, you had also accepted to create a default class as prescribed by your IDE and after writing your code in your own class, you are getting such an error. In order to eliminate this, go to the PROJECT folder → src → Default package. … Read more
I was using Java 8 and Intellij 2018.1.1 I solved the issue in this way: open IntelliJ Idea settings navigate to Build, Execution, Deployment > Compiler > Java Compiler Uncheck the option: Use ‘–release’ option for cross-compilation (Java 9 and later)
If anyone still getting this renaming MaxPermSize to MaxMetaspaceSize fixed the issue on my part, migrated from gradle7.2 to gradle8 with jdk11 previously, now on jdk17
Java 9 introduces the Cleaner and Cleanable utility classes which take care of wiring up phantom references to a queue and a cleaning thread draining that queue. While this lets you separate out the witness that will perform a post-mortem cleanup after the owning object has died, all the caveats about GC-triggered resource management still … Read more
Am I using the new module system correctly? Yes. What you are seeing is intended behavior, and this is because JPMS modules do not allow split packages. In case you are not familiar with the term “split packages” it essentially means two members of the same package coming from two different modules. For example: com.foo.A … Read more
Use //usr/bin/env jshell –show-version –execution local “$0” “$@”; exit $? as the first line of test.jsh. The test.jsh script could look like: //usr/bin/env jshell –show-version “$0” “$@”; exit $? System.out.println(“Hello World”) /exit The command line option –show-version is optional, of course, but gives immediate feedback that the tool is running. The extra command line option … Read more
Analysis First some random facts: if not given a class loader, JAXBContext::newInstance will use the thread’s context class loader when looking for the JAXB implementation – this is the case even if you call newInstance(Class…) (one might mistakenly think it uses the provided class instances’ loader) Tomcat builds a small class loader hierarchy to separate … Read more
Although the question was asking about the Object.finalize method, the subject really is about the finalization mechanism as a whole. This mechanism includes not only the surface API Object.finalize, but it also includes specifications of the programming language about the life cycle of objects, and practical impact on garbage collector implementations in JVMs. Much has … Read more