- Backported the DTD resolver from 2.3
- The resolver will now use intake.dtd on the classpath
if the DTD is http://jakarta.apache.org/turbine/dtd/intake_2_2_1.dtd
The DTD Resolver will now check the to see if the
URL for the DTD matched http://jakarta.apache.org/turbine/dtd/intake_2_3.dtd.
If so, the intake.dtd will be loaded from the classpath.
The intake_2_3.dtd has already be placed on the jakarta site.
Exceptions thrown while executing the "getter" method of
a mapped object were incorrectly reporting that the
problem occured while executing the "setter" method.
branches: 1.4.2;
Reverted the build process to the state before I
modified it to generate the OM classes for scheduler
service. I will put it back after the build process
is working properly AND xdoc generation is not broken
by the torque plugin.
Reverted the build process to the state before I
modified it to generate the OM classes for scheduler
service. I will put it back after the build process
is working properly AND xdoc generation is not broken
by the torque plugin.