Re: WebSite : Links to javadoc and component reference

2010-11-16 Thread Christian Riedel
I think it's a good idea... the search engines will be happy if you make sure the redirects are 301 and not 302! :-) Am 16.11.2010 um 17:22 schrieb Kalle Korhonen: > On Tue, Nov 16, 2010 at 2:20 AM, Christophe Cordenier > wrote: >> +1 for URL like >> http://tapestry.apache.org/stable/apidocs/e

Re: WebSite : Links to javadoc and component reference

2010-11-16 Thread Kalle Korhonen
On Tue, Nov 16, 2010 at 2:20 AM, Christophe Cordenier wrote: > +1 for URL like > http://tapestry.apache.org/stable/apidocs/etc > But why a redirect ? I don't get this point. Because search engines would then catch and use the version specific link,

Re: WebSite : Links to javadoc and component reference

2010-11-16 Thread Christophe Cordenier
+1 for URL like http://tapestry.apache.org/stable/apidocs/etc ... But why a redirect ? I don't get this point. 2010/11/13 Howard Lewis Ship > Two issues: > > Currently the 5.2 code builds to > http://tapestry.apache.org/tapestry5.2-dev/ ... I thin

Re: WebSite : Links to javadoc and component reference

2010-11-13 Thread Howard Lewis Ship
Two issues: Currently the 5.2 code builds to http://tapestry.apache.org/tapestry5.2-dev/ ... I think it's time to strip off the "-dev" suffix, since we are very close to a GA (not development) version. Also, I think it would be very useful to have either a symbolic link, or redirect, so that we c

WebSite : Links to javadoc and component reference

2010-11-13 Thread Christophe Cordenier
Hi I have seen links on Confluence's pages that refer to http://tapestry.apache.org/tapestry5/apidocs/ others use relative path (does not work in generated website) Any idea on how to handle this at last ? By the way, can we apply global replaces on Confluence ? -- Regards, Christophe Cordenier