On 10/13/07, Martijn Kruithof <[EMAIL PROTECTED]> wrote: > > Xavier Hanin schreef: > > On 10/12/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> > wrote: > > > >>>>> I don't want either, but ATM Ivy site is not integrated to > >>>>> > >>> incubator > >>> > >>>>> site, and Ivy is reachable at incubator.apache.org/ivy/. So why not > >>>>> take the same approach here? > >>>>> > >>>> We can do that as a first step and think about an integrated solution > >>>> later. If you check in your site into svn somewhere under > >>>> > >>> ant/ivy any > >>> > >>>> person with an Unix account in the Ant group can check it out to > >>>> people.apache.org and the site would go live. > >>>> > >>> We used to have our site in svn, but now we generate it and > >>> publish it using > >>> ssh. We have a build.xml for that, so we only need to change > >>> the destination > >>> location in the build.xml and publish the site, this should be > >>> pretty easy. > >>> > >>> One question: How do we handle relocation for people having > >>> bookmarked pages > >>> @ incubator.apache.org/ivy/? > >>> > >> Not sure if this is possible. > >> But maybe Apache httpd URL-rewrite could help... > >> > > > > > > Indeed, it seems to be possible. Here's what wicket guys use: > > .htaccess > > > ------------------------------------------------------------------------------- > > RewriteEngine on > > > > RewriteRule ^(.*)$ http://wicket.apache.org/$1 [R,L] > > > ------------------------------------------------------------------------------- > > Pretty easy to adapt to our needs :-) > > > > So I will move Ivy site if nobody objects. > > > > Xavier > > > > > Fine to move it, probably a moved permanently response (R=301) to the > browsers is better though. > > I currently have an update script on people (minotaur) that updates the > ant website once a day from svn. dependent on the location the ivy > specifics of the website will be stored the script will need to be > updated to do a separate sync for the ivy parts of the website. The > current sync is from /ant/core/trunk/docs for the base documentation and > /ant/core/tags/ANT_170/docs/manual for the manual part of the > documentation (this depends on the one doing an explicit checkout of a > certain branch at a specific position.) I assume the script would pick > up a new location after an explicit initial checkout. If not, I'll add it. > > (The script) > > #!/bin/tcsh > cd /www/ant.apache.org > /usr/local/bin/svn up | /usr/bin/grep -v "At revision"
The problem is that Ivy's site is stored in svn in a non generated form, which is browsable with a browser, but suffers from some problems of old browser compatibility and bad indexation by search engines. So the site we actually deploy is generated using an ant script. So if we want to make an automatic update it would need to do an svn up in a directory which is not the site itself, followed by a call to an ant script (which requires ant 1.7and java 6 for the use of javascript). I don't know if this is easy to do on people.a.o. Xavier Martijn > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://incubator.apache.org/ivy/ http://www.xoocode.org/
