How to solve the problem of no main manifest attribute caused by the updated version of springboot

How to solve the problem of no main manifest attribute caused by the updated version of springboot, in view of this problem, this article introduces the corresponding analysis and solution in detail, hoping to help more partners who want to solve this problem to find a more simple and feasible method.

Recently upgraded the springboot version to 2.1.6.RELEASESpringcloud version to Greenwich.SR2 push remote image to rancher has been unable to start, check the log shows no main manifest attribute, in / app.jar

Packaging tools have not been changed, there is no problem before, and then click the mouse packaging plug-in found that there is no version number!

Org.springframework.boot spring-boot-maven-plugin ${spring-boot.version} repackage

Add the version number and get it.

This is the answer to the question about how to solve the problem caused by the updated version of springboot. I hope the above content can be of some help to you. If you still have a lot of doubts to be solved, you can follow the industry information channel for more related knowledge.