But the error I am actually getting looks more sinister than an unused namespace. I get the following on every call to onvdl, followed by a large java traceback: ./run-onvdl p5valid.nvdl v.xml /home/syd/bin/onvdl DEBUG: executing 'java -Xss8m -Xmx4g -jar /opt/Oxygen_XML_Editor_23/lib/oxygen-patched-jing.jar p5valid.nvdl v.xml' WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by com.thaiopensource.validate.schematron.ISOSchemaReaderImpl (file:/opt/Oxygen_XML_Editor_23/lib/oxygen-patched-jing.jar) to constructor com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl() WARNING: Please consider reporting this to the maintainers of com.thaiopensource.validate.schematron.ISOSchemaReaderImpl WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/xerces/impl/locator/AttributeLocator at com.thaiopensource.relaxng.pattern.IdSoundnessChecker.idref(IdSoundnessChecker.java:165) That said, at first glance everything seems to have actually built OK. ________________________________ The errors we're seeing now, though, are from the Makefile; the nvdl stuff is run at line 191 and 192 of the Makefile, without any ant involvement. You can set failonerror on an ant call to exec, but the log parser is the only thing that will catch the Make stuff, I think. I notice that the nvdl schema includes the old Schematron namespace: <!-- foreign namespaces used in TEI --> <namespace ns="https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.ascc.net%2Fxml%2Fschematron&data=04%7C01%7Cs.bauman%40northeastern.edu%7C2adddfbe2c454fcb34fa08d8c6e37928%7Ca8eec281aaa34daeac9b9a398b9215e7%7C0%7C0%7C637478027897637837%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=VqPfXBMWFG4pahsArXGQnF0XJzJ%2BuD4reVMtsxbo1zA%3D&reserved=0"> <validate schema="schematron.rng"/> <attach useMode="allow"/> </namespace> <namespace ns="https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpurl.oclc.org%2Fdsdl%2Fschematron&data=04%7C01%7Cs.bauman%40northeastern.edu%7C2adddfbe2c454fcb34fa08d8c6e37928%7Ca8eec281aaa34daeac9b9a398b9215e7%7C0%7C0%7C637478027897637837%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=7mDV8RxTIRDP388MuzMU4Nw%2BIIOYJDifHbuDfjUHP3Y%3D&reserved=0"> <validate schema="iso-schematron.rng"/> <attach useMode="allow"/> </namespace> which we probably don't care about any more. I think it's a long time since anyone really looked at the nvdl.