Hi, On 3/20/06, Roy T. Fielding <[EMAIL PROTECTED]> wrote: > One idea was to move these generated files to a staging area and > reproduce from there, but that failed to generate enough volunteers > on site-dev (mostly because people insist on defending forrest or > maven or whatever as the uber-tool instead of just doing the work).
Ah, pity. It doesn't sound like it would be too complex to do something like that. I couldn't find site-dev archives for more details. Is the list private? > My guess is that the best way to handle this is to use Maven's > version of anakia to generate the site (for developers) but only > deploy a small subset of that to jackrabbit.apache.org (without > the reports, xref, etc.). OK, I think that's reasonable. How about if we also generated static javadoc and xref reports for each release? That should be good enough for the occasional user. We can also handle the alternating row issue with the following maven.xml addition: <postGoal name="xdoc"> <ant:replaceregexp match="<tr class="b">" replace="<tr class="a">" flags="g" byline="true"> <ant:fileset dir="${maven.docs.dest}" includes="**/*.html"/> </ant:replaceregexp> </postGoal> It makes the tables slightly less readable, but cuts down the amount extra changes. And as Roy mentioned, we could always compensate with extra CSS. BR, Jukka Zitting -- Yukatan - http://yukatan.fi/ - [EMAIL PROTECTED] Software craftsmanship, JCR consulting, and Java development