From: Wendy S. <ws...@gm...> - 2006-08-05 01:51:38
|
On 7/29/06, Herv=E9 BOUTEMY <her...@fr...> wrote: > I made 2 simple tests to see what using DTDDoc for Struts could look like= : ... > Is it what you were waiting for ? Or did you imagine another way of > integrating DTDDoc ? Sorry for the delay -- my 'todo list' is miles long. It looks great-- I had been trying to find the time to do exactly what you did to try it out. :) A few questions/comments: How significantly will we have to change the dtds? I need to go look at your docs again, but I was under the impression we would need to change the dtd comments to be more Javadoc-like. I think the sourceDirectory should default to src/main/resources and find any DTD anywhere under it. For example, taglib-maven-plugin [1] (which generates TLDDoc) defaults to src/main/resources/META-INF and any subdirectory. Although sourceDirectory is marked as optional in the docs, there is no default value listed, and I didn't get any output until I told it <sourceDirectory>src/main/resources</sourceDirectory> See above, that's what it should default to. :) Wish: It should support aggregation, so that if there are dtds scattered across different modules in the build, it can create one dtddoc set at the top level of the website. Wish: It should also support the notion of <includes>/<excludes> in case there are some dtds present in the filesystem that we do not want to build dtddoc for. The default font seems very small, is it easy to change? Thanks again! I'm going to add the config to the Tiles 2 project which is in the Struts Sandbox. That gives us a bit more freedom to play without affecting a release. [1] http://maven-taglib.sourceforge.net/m2/taglibdoc-mojo.html --=20 Wendy |