On 14/12/2007, Roland Weber <[EMAIL PROTECTED]> wrote: > 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.
Yes - the cgi passes the html through a Python script which fills in the blanks. But both have to be there. Actually the cgi file is the same for every project; just the name & location changes. > > 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. Yes. > > 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. Yes, that was my doing. I got fed up with seeing huge SVN diffs that did not relate to actual differences. Made it very tricky to tell if ones updates were correct before committing them... Dunno whether the Maven output will vary in the same way. But at present there are fewer people likely to do the build, so fewer possible combinations of software (or we may be able to standardise). > 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. > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
