My Maven Spring Boot project uses libraries that happen to have "Class-Path:" entries in their MANIFEST.MF. This seems to be a rather prehistoric (back from the 90s?) way of managing dependencies; it doesn't manage auto-downloads like maven, it doesn't consider versioning, publishing, or app assembling. Nowadays Maven manages all this behind the scenes in much better and simpler way for us.

However, when it comes to running the application using mvn spring-boot:run it shows the following warning:

WARN o.a.tomcat.util.scan.StandardJarScanner  : Failed to scan [file: /home/service/.m2/repository/g/a/1.0/b.jar] from classloader hierarchy
java.io.IOException: java.lang.reflect.InvocationTargetException
        at .apache.tomcat.utilpat.Jre9Compat.jarFileNewInstance(Jre9Compat.java:209) ~[tomcat-embed-core-9.0.45.jar:9.0.45]
        at .apache.tomcat.util.scan.JarFileUrlJar.<init>(JarFileUrlJar.java:65) ~[tomcat-embed-core-9.0.45.jar:9.0.45]
        …
        at com.cat.web. SpringWebAppStarter.main(SpringWebAppStarter.java:35) ~[classes/:na]
Caused by: java.lang.reflect.InvocationTargetException: null
        at java.base/jdk.internal.reflect.GeneratedConstructorAccessor20.newInstance(Unknown Source) ~[na:na]
        ... 46 common frames omitted
Caused by: java.nio.file.NoSuchFileException: /home/service/.m2/repository/g/a/1.0/b.jar

In this case the library g:a.jar (group and name simplified) has a META-INF/MANIFEST.MF file that includes:

Class-Path: b.jar

That is an optional library that is not really used by my app.

How can I tell Maven or Spring Boot to manage the dependencies by themselves only and to fully ignore the Class-Path: entries in the libraries' MANIFESTs?