fixed BUG-43532: jrxml translate build step fails if using jasperreport.dtd
Translate makes use of a custom EntityResolver to handle jasperreport.dtd resolving it locally instead of getting it from Internet. This local resolution is implemented making use of Class.getResourceAsStream method. The class the method was invoked from was java.lang.System.
Starting from JDK 9, getResourceAsStream invoked in classes within named Modules looks for the resources only in those modules rather than in the whole classpath [1]:
If this class is in a named Module then this method will attempt to find the resource in the module. This is done by delegating to the module's class loader findResource(String,String) method, invoking it with the module name and the absolute name of the resource. Resources in named modules are subject to the rules for encapsulation specified in the Module getResourceAsStream method and so this method returns null when the resource is a non-".class" resource in a package that is not open to the caller's module.
Otherwise, if this class is not in a named module then the rules for searching resources associated with a given class are implemented by the defining class loader of the class. This method delegates to this object's class loader. If this object was loaded by the bootstrap class loader, the method delegates to ClassLoader.getSystemResourceAsStream(java.lang.String).
As java.lang.System is in a named Module, dtd's resource was tried to be found within it and not found.
Fixed by invoking getResourceAsStream on LocalEntityResolver.class which is not in a named module.