|
I have hand-copied the two DTDs we currently publish (dialog.dtd and clay-config_1_0.dtd) to the "dtds" subdirectory, and set group write permssions appropriately. I'm going to leave this issue open, but take it off the 1.0.3 roadmap.
It hasn't synced yet -- did you rename dialog.dtd with the version number?
At Struts it's published as shale-dialog-config_1_0.dtd http://struts.apache.org/dtds/ I just changed the name (on the website) to "dialog_1_0.dtd". I don't think we need the "shale-" prefix because "shale" is already part of the website name.
Now, we also need to update the examples and docco to reflect the revised system identifier ... I'll go ahead and do that. As part of
See r427910 for antrun plugin config to copy in the dtds.
I'd like to move the Clay dtd into org/apache/clay/config and copy it to META-INF during the Clay build, rather than the other way around. This will allow us to copy everything in that directory instead of picking filenames out of META-INF which contains various other things, and it will be consistent with the location of the dialog dtd in shale-core. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Copying the dtds for the website (and the release distribution) was recently added to the Struts 1 build, and that config can be adopted for Shale.
(Publishing the dtds on the website was never part of the build process before, it was done manually.)