That way all your plugins and dependencies are defined in a single file and are not spread across multiple POM files what makes managing versions easier.

If your project is a multi-module Maven project then it helps to establish a parent POM and maintain dependencyManagement und pluginManagement in this file.

The first thing you should do before even thinking about upgrading the Java version is to clean up your pom.xml files. It includes everything I’ve learned while migrating our product to Java 11.Īs of 2019 Oracle Java 8 will no longer receive free security updates. Version 4.13 of rpm just doesn't seem to be available? I'm using CentOS7, but the same happens on RHEL 7.5 too.So you want to migrate to Java 11 but your Maven project is still sitting on Java 8? You don’t care much about the new module system (Jigsaw) introduced in Java 9, you just want your application to run on the latest JDK version? Then this guide is for you. Installation fails with: Error: Package: MYPACKAGE I thought rpm boolean dependencies might help, but I could find no information about updating rpm to version 4.13.

How do I set my packages' dependencies to be flexible enough to work with either java11? The Oracle Java 11 installer provides: $ rpm -qp -provides /tmp/jdk-11.0.2_linux-圆4_bin.rpm OpenJDK Java 11 provides: $ repoquery -provides java-11-openjdk I'm trying to create an rpm package with a dependency on java 11 however, it seems like the openjdk and Oracle java 11 packages don't provide any overlapping java virtual packages.