simply about difficult
If you working with IntelliJ IDEA you may notice, that changing Project’s JDK version is not affected to Gradle build/run. To force Gradle to use a specific JDK version / vendor you merely need to change Gradle JVM version in IntelliJ IDEA settings: Settings → Build, Execution, Deployment → Build Tools → Gradle → Gradle […]
READ MOREYou may encounter exception, that states: The reason is JDK/JRE version and vendor. I noticed, that at least JBR-17 (JetBrains Runtime) hasn’t got L32X64MixRandom algorithm. You may want to switch to Azul-17 (Azul Zulu) to make it works again. If you build/run your application with Gradle, don’t forget to change Gradle JVM version in IntelliJ […]
READ MOREYou may encounter a problem while building project: There may be at least two problems: Outdated version of gradle Too new version of JDK. Try upgrading Gradle / downgrading the JDK version to 1.8.
READ MOREFull error text: This error can be encountered if there are signed libraries among the dependencies of your project. To solve the problem, you need to exclude files with the extensions .SF, .DSA, .RSA from the build. Of course, we will assume that you are building uber jar (fat jar). We need to add a […]
READ MOREYou can get this error if you try to run jar without specifying the name of the class that contains fun main() and which you want to run. To do this, you need to register the full class name in the Main-Class key of your manifest. Plain jar without dependencies You need to replace the […]
READ MOREIn this article, we will find a solution to the question – how to make an uber jar Gradle Kotlin DSL or how to make a fat jar Gradle Kotlin DSL. Let’s add this to build.gradle.kts file: After that, you can build the jar with dependencies: That’s all. Possible errors Error: no main manifest attribute, […]
READ MORE