Restore publishing the dialog-config_1.0.dtd file (and any other DTDs defined by Shale)

• Key: SHALE-230
• Type: Bug
• Status: Resolved
• Resolution: Fixed
• Priority: Major
• Assignee: Wendy Smoak
• Reporter: Craig McClanahan
• Component/s: Website
• Affects Version/s: 1.0.2
• Fix Version/s: 1.0.4

Description

As part of our transition to the shale.apache.org website, it appears that publishing the DTD for dialog configuration (to subdirectory "dtds" on the website) got inadvertently dropped. It needs to be restored to the build process.

Comments

[Wendy Smoak]

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.)

[Craig McClanahan]

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.

[Wendy Smoak]

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/

[Craig McClanahan]

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.

[Craig McClanahan]

As part of SHALE-231 I am now publishing an Oasis catalog at <http://shale.apache.org/catalog.xml>. I've also manually deployed the relevant DTDs to the "dtds" subdirectory (as was past practice), but I'm going to leave this ticket open for potential automation later.

[Wendy Smoak]

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.