On 7/13/06, Craig McClanahan <crai...@apache.org> wrote:
I'm +1 on the change, but I'd also like to see us leave the physical
artifacts with the old names under the Struts website, as long as they're
willing to do that. Otherwise, we can set up HTTP redirects that point at
the correct places in the Shale website.
I'm vaguely concerned that the tools that are using those dtds (mostly
validating editors, I think,) won't be able to handle redirects. I'd
like to see what JEdit does, at least.
The Shale DTDs can stay there at Struts until we figure out how best
to handle it.
For the Shale website, I do think we need a "dtds" directory that is part of
the website build, and which includes the physical artifacts we're talking
I added that to Struts 1 the other day... though now that I think
about it, I'm not entirely sure why I introduced a /resources
directory instead of just copying them to a /dtds directory! I'll
change it, and then do the same thing for Shale.
The DTDs and schemas should live under src/main/resources in the
module they belong to, so they'll be in the right place in the jar
file, and we'll use antrun to copy them for the website.