Recently, the springboot version was upgraded to 2.1.6. Release , and the springcloud version was upgraded to Greenwich. Sr2 when pushing the remote image to Ranger, it has been unable to start. The log shows no main manifest attribute, in/APP. Jar

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

  <plugin>
	  <groupId>org.springframework.boot</groupId>
	  <artifactId>spring-boot-maven-plugin</artifactId>
	  <!--Be sure to match the springboot version number, because the new version of springboot no longer sets the dependencies of this plugin-->
	  <version>${spring-boot.version}</version>
	  <executions>
		  <execution>
			  <goals>
			  	<goal>repackage</goal>
			  </goals>
		  </execution>
	  </executions>
  </plugin>

Add in the version number and it’s done

Similar Posts:

• Unable to find a single main class from the following candidates [xxx，xxx]
• [Solved] SpringBoot Project Package to jar Error: ClassNotFound…
• How to Solve Error: spring-boot-maven-plugin not found
• [Solved] SpringBoot Package Error: Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-res
• SpringBoot Project Package Error: [ERROR] Failed to execute goal org.springframework.boot:spring-boot-maven-plugin (Running Normally)
• [Solved] Plugin ‘org.springframework.boot:spring-boot-maven-plugin:’not found
• [Solved] Spring Boot Package Error: Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0
• Failed to execute goal org.springframework.boot:spring-boot-maven-plugin:2.3.5. RELEASE:repackage (repackage) on project tristone-boot-module-system: zip file is empty
• Maven no main manifest attribute when generate jar for project
• Unregistering JMX-exposed beans on shutdown Solution