One thing that just came to mind is if you do the build without tests. Then update the CLASSPATH once the jars are done and then run the tests after that. Could all be done in the build.xml I think by setting a different CLASSPATH on the Java invocation for the tests.
Thanks, ~Roger > On Nov 29, 2023, at 8:53 AM, Sandro Martini <sandro.mart...@gmail.com> wrote: > > Ciao Roger, > thanks for the help; I'll try to update the CLASSPATH in the sample setup > shell script (and update it in SVN); otherwise in the worst case check if > such tests can be disabled when there are no jars (if possible). > I'll keep you updated. > > Bye > > >> Il giorno mar 28 nov 2023 alle ore 23:28 Roger Whitcomb < >> rogerandb...@rbwhitcomb.com> ha scritto: >> >> Ciao Sandro, >> Thanks for this. All three tests that fail are due to the same root cause: >> the tests are being run from the .class files and not from the .jar files. >> The VersionTest fails because >> Version.class.getPackage().getImplementationVersion() returns null (because >> the class isn’t inside a .jar file and therefore has no package version). >> Similarly, GaugeTest and MeterTest fail because there is no ServiceProvider >> for “Theme” (which only exists inside the .jar file manifest). >> >> I’m thinking this is a setup issue with the CLASSPATH … but I’m not sure >> how to fix it … >> >> Thanks, >> ~Roger >> >> On Nov 28, 2023, at 11:48 AM, Sandro Martini >> <https://urldefense.proofpoint.com/v2/url?u=http-3A__sandro.martini-40gmail.com&d=DwIFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=NGXYnxeSiI_cX848yMIhm_nxVirU2qvwSBiomy8msDM&m=mk5jhMR5lMYXEbejeJc5Js5h6JGBh4RF82P3a234fyTgeJJjAjeOwgoQKOGOfVJk&s=_reMdFUU0TiF9MRFOiVd_ciR7ybmxqd4VwKYolPo7wM&e=> >> <mailto:sandro.mart...@gmail.com>> wrote: >> >> <pivot-trunk_tests_verbose.txt> >> >>
