Hi Sebastian, >> The alternative to all-Maven is to use Maven only for the sites >> in the deliverables (HttpClient 3.1, HttpCore, HttpClient 4.0) >> and to use the XSLT or Anakia approach for all online-only pages. >> I really haven't made up my mind yet. > > Maven does seem to be good for site building; it produces some useful > reports which might be hard work otherwise. e.g. the Xref looks nice. > > I think the sites in the deliverables should be a subset of the > web-site, not something completely different.
That's what I meant, sorry for not being clear about this. HttpClient 3.x ships with a full copy of it's site: http://jakarta.apache.org/httpcomponents/httpclient-3.x/ HttpCore and HttpClient 4.0 currently do not contain the respective component site, but that's something we can change: http://jakarta.apache.org/httpcomponents/httpcomponents-core/index.html http://jakarta.apache.org/httpcomponents/httpcomponents-client/index.html The project/ folder in SVN holds the part of our current site that is not tied to a deliverable (=component): http://jakarta.apache.org/httpcomponents/ So when I wrote "sites in the deliverables", I meant that we could use Maven to generate and deploy the component sites online as well as package them in the deliverables themselves. But everything above the component level could be generated with XSLT or Anakia. cheers, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
