commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Phil Steitz <phil.ste...@gmail.com>
Subject Re: [commons-build] Site build problem
Date Mon, 12 Sep 2005 13:21:37 GMT
On 9/11/05, Niall Pemberton <niall.pemberton@blueyonder.co.uk> wrote:
> 
> ----- Original Message -----
> From: "Brett Porter" <brett@apache.org>
> 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.


The menus actually come from the xml entities that are (individually) 
referenced from the navigation.xml files. 

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


This is the reason that commons-build was created in the first place. 

I will do as you suggest above, for the immediate term (create two versions, 
with notes), this evening.

FWIW, I now recall that the reason that main reason that most of us decided 
to stop extending the commons-build POM was that it made distribution 
awkward.

I will also have a look at how different things look bet 1.8, 1.9 with 
maven.xdoc.theme=classic. These should not be much different and, if so, I 
think I agree with Brett that the best solution would be to just toss 
commons-site.jsl together, replacing the funny out-links using css or 
something. IIRC, that was the only real complaint. 

Phil

Niall
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> 
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message