The Class-Path manifest attribute in [path] referenced one or more files that do not exist

Question

I am having a problem with Java 11/Spring Boot 2.1 migration where the project compiles but when run returns only:

Connected to the target VM, address: '127.0.0.1:5754', transport: 'socket'
The Class-Path manifest attribute in C:\Users\{user}\.m2\repository\xalan\serializer\2.7.2\serializer-2.7.2.jar referenced one or more files that do not exist: 
file:/C:/Users/{user}/.m2/repository/xalan/serializer/2.7.2/xml-apis.jar
The Class-Path manifest attribute in C:\Users\{user}\.m2\repository\xalan\xalan\2.7.2\xalan-2.7.2.jar referenced one or more files that do not exist: 
file:/C:/Users/{user}/.m2/repository/xalan/xalan/2.7.2/xercesImpl.jar,file:/C:/Users/{user}/.m2/repository/xalan/xalan/2.7.2/xml-apis.jar,file:/C:/Users/{user}/.m2/repository/xalan/xalan/2.7.2/serializer.jar
Disconnected from the target VM, address: '127.0.0.1:5754', transport: 'socket'

Process finished with exit code 1

I have tried updating maven versions, maven compiler version, etc.

How do I fix this?

Answer 1

Please check do you have "spring-boot-devtools dependency" in pom.xml then remove it and try again

Answer 2

I had a similar problem after changing my logback-spring.xml file.

The application wouldn't start anymore and I could only see some INFO messages like those you described but that wasn't the actual cause of the problem.

The application was failing after that point but couldn't log any erros messages exactly because of a issue in my logback-spring.xml.

So if you don't see any other error messages, try to double check that your logging mechanism is configured correctly.

Answer 3

Since this question continues to get traffic, I will post a summary of the answers and comments -

The messages described in the title are warnings, not errors, and should not be causing your app to crash.

If your app is crashing, check for errors earlier in the logs which would cause it to exit.

In cases where no error output was available, several people reported the issue was caused by an outdated dependency which needed to be updated as part of their Spring/Spring Boot/Java upgrade.