[DELTASPIKE-1372] Test-Control module has a undeclared and undocumented de-facto runtime dependency on core-impl

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.9.0
• Fix Version/s: 1.9.1
• Component/s: TestControl
• Assignee: Unassigned
• Reporter: Juri Berlanda
• Created: 13/Mar/19 15:39
• Updated: 19/Aug/19 09:51
• Resolved: 25/Mar/19 10:29

Description

When setting up Test-Control Module like described in http://deltaspike.apache.org/documentation/test-control.html I end up with:

java.lang.ExceptionInInitializerError
{{ at org.apache.deltaspike.testcontrol.api.junit.CdiTestRunner.<clinit>(CdiTestRunner.java:87)}}
{{ at org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:104)}}
{{ at org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:86)}}
{{ at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:26)}}
{{ at org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:33)}}
{{ Caused by: java.lang.RuntimeException: Could not load ConfigProvider}}
{{ at org.apache.deltaspike.core.api.config.ConfigResolver.getConfigProvider(ConfigResolver.java:628)}}
{{ at org.apache.deltaspike.core.api.config.ConfigResolver.resolve(ConfigResolver.java:613)}}
{{ at org.apache.deltaspike.testcontrol.api.junit.TestBaseConfig$ContainerIntegration.<clinit>(TestBaseConfig.java:29)}}
{{ ... 15 more}}

The reason is, that deltaspike-core-impl is missing on the classpath. Adding it solves the problem.

So imho. we should add a runtime dependency on deltaspike-core-impl to deltaspike-test-control-module-impl. It should be a matter of replacing <scope>test</scope> to <scope>runtime</scope> on deltaspike-core-impl in deltaspike-test-control-module-impl's pom.xml.

I'll create a pull-request doing exactly that in a moment.

EDIT: Pull-request exists at https://github.com/apache/deltaspike/pull/86

Issue Links

• links to: GitHub Pull Request #86