----- Original Message ----- From: "Brett Porter" <[EMAIL PROTECTED]> Sent: Monday, September 12, 2005 2:36 AM
> I think this option I raised earlier got missed, so I'll repeat here: > > The one option I'd consider is whether it is worth ditching > commons-site.jsl altogether. I have no idea what it adds: > setting maven.xdoc.theme=classic instead looks the same to me (except for the > addition of the the external link icons which can be removed through > CSS). If you'd like me to commit that for commons-math I can. > > Does anyone know what it was meant to do, other than insulate against changes > in the Maven generated site? One thing it does is add the standard commons "About Us" menu before the project menu. > I know that doesn't solve the fundamental problem in the plugin, but > might be the best solution for commons. IMO we would still need have a dependency on a specific xdoc plugin version - otherwise what different components' sites look like could vary depending on what version plugin happened to be installed. Niall --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
