spring-framework: Classpath scanning does not work in tests using the module path [SPR-16977]
Andy Wilkinson opened SPR-16977 and commented
It appears the classpath scanning doesn’t work when Surefire launches the JVM configured to use the module path. target/classes is placed on the module path and target/test-classes is patched into this module but classpath scanning only finds classes in target/test-classes.
I have attached a minimal sample that should reproduce the problem when built (mvn test) with Java 10. The sysout from the test should show that only the test class has been found:
[INFO] Running com.example.ScanningTest
[file [/Users/awilkinson/dev/temp/module-path-scanning/target/test-classes/com/example/ScanningTest.class]]
To my rather untrained eye, building with -X and examining the arguments that Surefire uses to launch the forked JVM (in target/surefire) suggests that Surefire’s configuration of the JVM is correct.
When the sample is modified to work with Java 8 (remove module-info.java and change the compiler plugin configuration to remove <release>10</release>) the class in target/classes is also found:
[INFO] Running com.example.ScanningTest
[file [/Users/awilkinson/dev/temp/module-path-scanning/target/test-classes/com/example/ScanningTest.class], file [/Users/awilkinson/dev/temp/module-path-scanning/target/classes/com/example/One.class]]
Affects: 5.0.7
Reference URL: https://github.com/spring-projects/spring-boot/issues/13581
Attachments:
- module-path-scanning.zip (3.66 kB)
Issue Links:
- #20937 Compatibility with JDK 11
2 votes, 7 watchers
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 26 (4 by maintainers)
I had the same (or very similar) issue running tests with maven-failsafe-plugin 3.0.0-M5 on AdoptOpen JDK 11. The work around is to disable using module path in plugin’s configuration
<useModulePath>false</useModulePath>Another year has passed. To me this still is a showstopper.
If you’ve been following this issue, I’m happy to let you know that #28506 has been resolved for inclusion in 6.0 M5.
In the interim, feel free to try out 6.0 snapshots with modular testing using Maven.
I’ve created a new repository for demonstrating the use of the Spring Framework with the Java Module System: https://github.com/sbrannen/spring-module-system
That repository currently contains a
maven-surefire-patched-moduleproject which demonstrates support for@ComponentScanin a patched module using Maven Surefire.I should mention that I am also suffering from this issue and it would really be appreciated if this could be solved by Spring if it is not going to be solved by Java itself.
FYI, I had similar classpath issues when I introduced java modules in my project and executed the Spring Boot unit tests.
I eventually got the test executed successfully by including within the configuration of SureFire version 2.22.x
<forkCount>0</forkCount>.Hi everybody,
Thanks for all of the feedback over the years!
I am now closing this issue since it has been superseded by the following issues.
Please follow those issues for additional updates on module path scanning and resource support.
Disclaimer: This is in no way production ready code. This is 100% “proof of concept” code.
Now, having said that… with an updated version of the original example application from @wilkinsona (now using Java 17, Maven 3.8.5, Maven Surefire 3.0.0-M6, Spring Framework 5.3.20, and JUnit Jupiter 5.8.2), I have come up with the following.
The output of running that is:
The first output demonstrates the issue:
PathMatchingResourcePatternResolveronly findsScanningTest.classand notOne.class.The final output demonstrates that we can find resources (as instances of
URI) using theModuleAPIs and successfully find bothScanningTest.classandOne.class.Kudos to @sormuras for providing inspirational use of the
java.lang.moduleAPIs in JUnit 5!Where to go from here?
We may introduce a new
ModulePathResourceas a companion toClassPathResource, where the logic inModulePathResourceis similar to the logic in the above proof of concept.We may then introduce additional support in
PathMatchingResourcePatternResolverthat resolvesModulePathResourceinstances when appropriate.Thomas Kratz commented
Are there any plans to resolve this like recommended?
Would doFindAllClassPathResources(String path) be the point to put that? I don’t clearly understand that suggestion, but maybe I could invest some time over the holidays.
I would still think this is a JDK issue.