Marcel Offermans wrote: > I currently see a couple of options: > > a) Use a download.cgi script that is modified a bit so the html file it > parses does not need to be in the same directory (but in one we can > supply in the script). Unfortunately, my python/cgi skills are not > sufficient to see if this is easily possible. I would like: > http://host/download.cgi?template=http://otherhost/downloads.html > Hmm, ok, we could pass this on to infrastructure, perhaps they are willing to help us out here.
> b) Deploy the download.cgi and download.html files somewhere else, and > include them in a Confluence page with (for example) an iframe. This > would at least give us some freedom in modifying the site through > Confluence. > > Option a) would be the best (at least for now) if that can be done easily. Don't know either - option b) is easier, but a) is better, I agree. > > By the way, is there some consensus about how to make older versions > available? I mean, do we need a "download" page per release? Ideally I > think we would like to automate this as much as possible. Does it make > sense to generate the download.cgi and download.html as part of a > "release" target, together with all other artifacts, so we can just copy > all of them to dist/ (or dist/versionX.Y.Z/) and go from there? The consensus about older versions is that they are only available from archive.apache.org. So usually we just put a link for the latest version on the download page and a general link to "older versions" pointing to archive.apache.org/dist/felix. Several projects use the "latest" suffix, so they put a something-x.y.zip into the dist folder and create a soft link something-latest.zip pointing to this. From the download.html, they always just refer to something-latest.zip. > > Expanding on that "automating" point, it would be nice if the artifacts > we generate using our continuous build could be "released" easily. This > would go for both our source and binary releases, but probably also for > "generated" documentation related to those releases (javadoc, unit test > and coverage results, etc.). We can do this with maven and the deploy plugin. We can deploy to several locations during release and put different things there. > > Another question, when I log in to people.apache.org, what folder should > I go to to modify files that appear in www.apache.org/dist/felix/ ? I > thought I found the directory (/www/www.apache.org/dist/felix/) but > stuff I put in there did not show up (unless it takes some time for them > to show up?). Yes, that's the correct directory and yes :) it takes some time - I sync the pages are synced every two hours. So how do we proceed? I'll ask infrastructure if someone can change the script for us. In the meantime, we could put the download.cgi and download.html to felix.apache.org and point to that. WDYT? Carsten -- Carsten Ziegeler [EMAIL PROTECTED]
