dashorst opened a new issue, #1863: URL: https://github.com/apache/wicket/issues/1863
`testing/wicket-threadtest` and `testing/wicket-arquillian` are in the repository but not in the reactor, so nothing builds or tests them. Decide whether to delete them or bring them back into the build. - `testing/wicket-threadtest` (Wicket Thread Test) was dropped from the module list in 2011 by WICKET-4281 (2483b58f25). It runs load-style tests against two small apps using HttpUnit and JUnit 4. - `testing/wicket-arquillian` (WICKET-5926, 2015) was removed from the module list in 2019 (a4b92a4322) because it caused port clashes on BuildBot and slowed down the build. The commit kept it "for anyone who wants to use it as inspiration". Its README still describes Wicket 7.x on WildFly with Java EE 6. Both poms still name `10.0.0-M1-SNAPSHOT` as their parent version, so neither has been built since Wicket 10 development started. They are the only users of `junit-vintage-engine` and, along with wicket-examples, of HttpUnit (last released 2018), both of which the root pom still manages. Options: 1. Delete both modules and drop the managed dependencies only they use. 2. Bring them up to date and back into the build. For wicket-arquillian that means fixing the port clash; for wicket-threadtest, moving off HttpUnit and JUnit 4. 3. Keep only one of them. Found during the dependency audit in #1862. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
