Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Not A Bug
-
2.17
-
None
-
None
Description
When using the test-jar functionality, the test dependencies declared in the test jar are not added to the runner's classpath, leading to NoClassDefFoundErrors (or silent failures to match annotations on any test methods) when running the client project. Explicitly declaring a dependency on the upstream project does not help. Overriding the dependency scope on the upstream's dependencies to compile causes the client project to resolve the dependencies.
I expected the client project to pull in the test dependencies needed by the upstream project when running its tests.
Attachments
Issue Links
- is blocked by
-
SUREFIRE-1034 dependencesToScan versus classifiers: what's the scoop?
- Closed
-
SUREFIRE-1004 Enhance pattern/wildcard capabilities for dependenciesToScan to GAVT
- Closed