Community
Participate
Working Groups
I followed the recommended workaround, by using 'file:' prefix in my system entities, and it only solved half of the problem (as described in bug 20819 fix) Here is the case : I have a build.xml file with a DOCTYPE referencing a project.dtd located in another directory, by a relative path (file:../build/project.dtd for instance). At this point it works fine. Project.dtd is found correctly. But I have an issue with my project.dtd itself, which also declares a SYSTEM entity referencing an XML file located in the SAME directory (the project.dtd dir) with a relative path (let's say file:./rules.xml). The resolver still processes the dtd file in the build.xml working dir and therefore do not find my rules.xml file. It seems that the relative URI inside INCLUDED DTD files are not evaluated using DTD resource location as base path, but using the location of the file including the DTD.
Do you only see this problem in the UI (i.e. when displaying the targets) or does it also happen when you just run the Ant build file? In release 2.0, we were parsing the XML file ourselves to get the targets instead of relying on the Ant framework. In release 2.0.1, we are switching to using the support from the Ant framework.
It only happens in the UI, it works fine when running Ant build file in external tools.
Then it will be fixed in the 2.0.1 release. It will also be part of the 2.1 integration builds in the near future. *** This bug has been marked as a duplicate of 20819 ***
