On Wed, 05 Aug 2020 09:55:57 +0200 Matthijs Kooijman <matth...@stdin.nl> wrote: > > If my analysis is correct, could you make the changes so > ant-junitlauncher is included?
Hello, the good news is, adding that module is not a big deal. I think I have done that correctly. Even better, it gets rid of the specific error you reported! However, that does not make josm test successfully for me. I get another message that could either mean I built ant-optional not correctly or there is something weird going on in josm: test: [echo] Running unit tests with JUnit [junitlauncher] Error: Could not find or load main class org.apache.tools.ant.taskdefs.optional.junitlauncher.StandaloneLauncher [junitlauncher] Caused by: java.lang.ClassNotFoundException: org.apache.tools.ant.taskdefs.optional.junitlauncher.StandaloneLauncher The documentation of StandaloneLauncher hints at it should not actually be used externally. However, it is referenced in JUnitLauncherTaskTest.java (which is part of the exposed/"confined" classes) in a test... it's a bit weird. Since there is some discussion about a newer ant release in some of the josm tickets with similar problems I tried updating to the currently available upstream releases (1.10.10 and 1.10.11) but it doesn't fix that issue. One of the devs pointed me to the CI configuration that builds on Ubuntu. Maybe there is some hint in there but I dont see it... https://github.com/openstreetmap/josm/blob/master/.github/workflows/ant.yml I am out of ideas. At least it builds fine and is executable... -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner
