How to solve the loss of xml files encountered by SpringBoot in jar package

Today, I will talk to you about how to solve the loss of xml files encountered by SpringBoot in jar package. Many people may not know much about it. In order to make you understand better, the editor has summarized the following content for you. I hope you can get something according to this article.

The xml file encountered by SpringBoot in jar package is missing. Add the following to the build tag of pom.xml

Specify resource path

Src/main/java * * / * .xml true src/main/resources * * / *. Some problems encountered by SpringBoot in typing jar package 1. Unable to access jsp page 1.1There is no jsp file in the jar package. 404 error reported

Reason: no jsp packaging path has been added

Solution: add the following code to pom.xml

Src/main/resources * * / * false src/main/java * * / .java Src/main/webapp META-INF/resources * * / * * 1.2 still cannot access the page But do not report an error, it has been loading.

Cause: maven compiled version problem

Solution: change the version to 1.4.2.RELEASE (currently only this version can parse jsp with jar package)

1.3 if you still report an error at this time

Failed to execute goal org.springframework.boot:spring-boot-maven-plugin:1.4.2.RELEASE:repackage (default) on project fulan-demo: Execution default of goal org.springframework.boot:spring-boot-maven-plugin:1.4.2.RELEASE:repackage failed: Unable to find a single main class from the following candidates

Reason: no location of startup class specified

Solution: specify the startup class in pol.xml

Com.xxx.xxx.xxxApplication after reading the above, do you have any further understanding of how to solve the loss of xml files encountered by SpringBoot in jar packages? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.