At first I thought there was a problem here, and later I couldn't pack mapper.xml in.
This is an unusual message from the newspaper.
MyBatis start always reported binding error (unable to find the corresponding SQL configuration mapper), after some Google did not solve the problem (everyone said that XML did not write to the kind of), there is no suspicion of missing the XML file, finally forced to look at the next After Maven packaged the war file, only to find the problem.
Not much nonsense, the solution is to add the following code to the build node in the Pom.xml file:
<build>
<resources>
<resource>
<directory>src/main/java</directory>
<includes>
<include>**/*.properties</include>
<include>**/*.xml</include>
</includes>
<filtering>false</filtering>
</resource>
<resource>
<directory>src/main/resources</directory>
<includes>
<include>**/*.properties</include>
<include>**/*.xml</include>
</includes>
<filtering>false</filtering>
</resource>
</resources>
</build>
As long as the report resource marked as a resource file, there will be no problem without joining the related packaging under the resource file.
Record idea MAVEN Project package Deployment Web project Mapper scan failed