Hello Sebastian, >> 1. the download pages >> http://jakarta.apache.org/site/downloads/downloads_httpcomponents-httpcore.cgi >> http://jakarta.apache.org/site/downloads/downloads_httpcomponents-httpclient.cgi >> http://jakarta.apache.org/site/downloads/downloads_commons-httpclient-3.x.cgi > > Also need the corresponding html files.
The html files seem to be templates for the cgi. At least the "Change" button on the html version only triggers errors, and the drop-down list looks like it contains just placeholders. > These are both currently autogenerated using XSLT. > >> 2. Bylaws & Guidelines >> http://jakarta.apache.org/site/management.html >> http://jakarta.apache.org/site/guidelines.html >> + some referenced from guidelines.html >> http://jakarta.apache.org/site/mail.html > > OK - some of this material could perhaps be pushed up to ASF level, > but given that Jakarta did not do it... Maybe it has to do with the fact that PMCs are expected to define their own bylaws and modes of operation. A lot of the stuff on these pages needs to be filtered of course, but some seemed useful. > Indeed - there does not seem to be an SVN copy of the site with Maven, > so if it gets lost/damaged it has to be regenerated as far as I can > tell. > > The Jakarta way makes it easy; can get everything ready in SVN first, > and then update the site. And you can svn diff which files have actually changed. > It's also easy to detect if the site files have been editted directly; > as the Maven stuff is not in SVN there's no easy way to check for > changed, missing or additional files. > > But perhaps one can combine the two approaches? > Use Maven to generate the site, and rather than upload it directly, > store it in SVN. One can use Maven to deploy to a staging location. But iirc, the Jakarta XSLT stuff also has some additional processing to normalize the generated files. Otherwise, generated files may differ (depending on JDK/XSLT/OS used) even though the content is identical. 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. cheers, Roland >> And what is your preferred pathname for the 3.1 site? >> http://hc.apache.org/httpclient-3.x/index.html > > +1 (counted :-) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
