I have a concern about the default classpath order when executing the test task. It seems that test/classes is added before test/resources. This can be a problem (and is a problem for us), since we use pattern matching expressions when defining resources to be loaded by Spring.
Spring will not find these resources since it first finds the test/classes folder on the path which does not contain these xml files (they are located under test/resources).
I know that I could use classpath*:/… to patch this problem, but it is not really an option for us to change over a hundred xml configuration files while migrating from Maven to Gradle. Also, Gradle should not dictate how I have to define my pattern
I guess an easy solution is if we could fix (switch) the classpath order of test/classes and test/resources. Any suggestions on how we can achieve this? (a similar question has been posted by my colleague).