The new svn layout for the site is done. I think I got it working correctly. You're welcomed to test it and check that I didn't missed anything.
For Ivy and IvyDE site build, it works like the old one, but each has now its own folder and build. For Ant's site, there's no more need of having somewhere an anakia installed, it is provided within the site. So to generate the site, running just "ant docs" is sufficient. And about the inclusion of the manual into the website, I have created an svn:externals from /ant/site/ant/staging/manual to https://svn.apache.org/repos/asf/ant/core/tags/ANT_182/docs/manual/. So we'll get the last released manual online. So now I'll ask the infra about setting up a publication of theses staging branches to an ant.staging.apache.org via svnpubsub. Then we'll review the site online. And once we are happy with the result, we would then proceed with creating the production branches from the staging ones and open another ticket for the infra to get thoses branches published to ant.apache.org. Nicolas Le 1 mars 2011 à 17:41, Nicolas Lalevée a écrit : > > Le 1 mars 2011 à 16:33, Stefan Bodewig a écrit : > >> On 2011-03-01, Nicolas Lalevée wrote: >> >>> I don't know much about Anakia, but would it handle correctly renamed >>> paged ? Would it correctly delete the html files corresponding to the >>> removed xdoc pages ? >> >> We don't remove or rename pages ;-) The whole internet would collapse if >> people suddenly started to remove pages that other people link to, you >> know? > > :D > I forgot about that, thanks for the reminder ! > >> >>> And would it handle correctly that if you change only the template, it >>> has too regenerate the entire site ? >> >> Sometimes it does, but not always. I can't remember which way around it >> is. Either it regenerates everything if you change priject.xml but >> doesn't do so if you change the .vm files or the other way around. > > So if it works enough correctly, we could setup a buildbot. I suggest we'll > look into it after the layout change and the setup of svnpubsub (if there's > still no objection). > >> >>> About ant's doc, maybe we do like Ivy. Ivy does embed its doc into the >>> distribution while also exposing it on the website. In svn, the Ivy >>> docs (the source, not the generated html files) are maintained here: >>> https://svn.apache.org/repos/asf/ant/ivy/core/trunk/doc/ And in the >>> source of Ivy's site, there is a svn:external in >>> https://svn.apache.org/repos/asf/ant/ivy/site/history/ >> >> That would work. We'd even only need the externals in the tags/branches >> for releases. >> >>> And I just found that : https://svn.apache.org/repos/asf/ant/site >>> What its status, its history ? >> >> Status: dead. >> >> Its history[1] is an attempt to pull together the Anakia generated pages >> from trunk and the manual from the latest release while providing all >> the stuff needed to run Anakia. This was created around the time we >> released the first Antlibs as I envisioned they'd create bigger websites >> themselves (i.e. more than one page) - this never happened. >> >> For reasons I can't remember I ran out of steam before finishing the >> idea. Antoine used to update this part from time to time but in reality >> it turned out to be easier to just keep everything in trunk and forget >> about the separation. > > ok. Hopefully this time we'll get it working. > > Nicolas > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org > For additional commands, e-mail: dev-h...@ant.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
