add properties checkMapperMethodRelatedMappedStatementExist to find bug as soon as possible, false as default value ,when setting true ,this will check mapper method related mappedStatement whether exist when application startup ,exception throw when related mappedStatement not exist.
improve pr :https://github.com/mybatis/mybatis-3/pull/1506
Comment From: harawata
There seems to be many unrelated changes in this PR. Please check again.
Comment From: yangjianzhou
some unrelated code change to make test cases passed
Comment From: harawata
Um...you cannot do that because it means that your PR breaks backward compatibility. 😖 If it's difficult to fix those broken tests, we may have to close this PR.
Comment From: yangjianzhou
I add those unrelated code to make test case passed ,because those test case run fail after my code committed.
Comment From: yangjianzhou
as you can see this commit(https://github.com/mybatis/mybatis-3/pull/1534/commits/6fdd4f874493f61cb2d241f4df6b18c1247833f9): make test passed
Comment From: harawata
Yes, I am aware. One of the purposes of test cases is to prevent new changes from breaking backward compatibility. If a test failed after you changed something, some existing functionality stopped working because of your change. So, your commit 6fdd4f874493f61cb2d241f4df6b18c1247833f9 is basically hiding the breakage and that is not acceptable.
Hope this explanation is clear enough.
Comment From: yangjianzhou
another pr(https://github.com/mybatis/mybatis-3/pull/1555) has committed and as same as this one , and without test case ,so close this pr.