But my question is: why does it scan the test folder? (/ Src / main / test) .
The context configuration is as follows:
<jpa:repositories base-package="com.domain.repository" />
To be precise, I don't think Spring scans this folder - this is your source folder after all. It only considers the expanded package structure, and my suspicion will be that the cause of the problem has something to do with it.
I ran into the same problem, but was caused by an erroneous deployment configuration in Eclipse, and not something specific to Spring. I had Eclipse configured to deploy my test classes to src/test/java in the target deployment package, so all the test files (which, of course, had the appropriate package structures) were present when the server started. However, judging by the .classpath you posted, I see that you explicitly exclude them from the deployment.
However, there are other ways that class files can infiltrate your deployment. Have you been able to verify that the test classes are not actually in the deployed package? Can they be synchronized there by another process that you configured (possibly the FileSynch plugin)?
Also, do you have any other Spring context files with configurations for scanning other base packages?
You can add more details about your Eclipse configuration and how you are deploying to your test server to help solve the problem.
chrisjleu
source share