[
https://issues.apache.org/jira/browse/WICKET-7019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17724496#comment-17724496
]
Andi Huber commented on WICKET-7019:
------------------------------------
Around Mar 14, 2023 Surefire 3.0.0 was released, which now supports an option
to disable module-path for testing.
https://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#usemodulepath
This solves our build/test issues.
> [Not an Issue] Remove Junit Jupiter from module path (JPMS)
> -----------------------------------------------------------
>
> Key: WICKET-7019
> URL: https://issues.apache.org/jira/browse/WICKET-7019
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-core
> Affects Versions: 10.0.0
> Reporter: Andi Huber
> Priority: Major
>
> With Wicket Core's WicketTester on the module path, consuming projects that
> also use JPMS are forced to change their junit-jupiter-engine dependency
> scopes from 'test' to 'compile' (Maven speak.) Which in our case does break
> corresponding surefire tests no matter what.
> So the desired solution would be to split out WicketTester from wicket-core
> into wicket-core-tester say and don't put that artifact on the module path,
> use an automated module name instead.
> As a proof of concept, I forked off on Wicket 10.0.0-M1-SNAPSHOT, kept
> everything on the module path as is, just removing Jupiter, hence had to
> split out WicketTester into its own artifact. And also split up wicket-util
> into 2 artifacts. But thats it.
> For reference the fork can be found here
> https://github.com/apache-causeway-committers/wicket. (Its stripped off the
> artifacts we don't care about. So not a merge candidate, but to show it can
> be done.)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
