Basically, I want to keep the urls we have today for the latest released version. For example: http://mojo.codehaus.org/awesome-maven-plugin A user accessing this url should see the latest site. He/she should not be redirect to (for example): http://mojo.codehaus.org/setup-maven-plugin/2.3 as that would then be the url he/she would bookmark. And that's going to cause confusion when we release 2.4+.
/Anders On Wed, May 25, 2011 at 12:41, Benson Margulies <[email protected]>wrote: > On Wed, May 25, 2011 at 6:37 AM, Anders Hammar <[email protected]> wrote: > > By "map" do you mean a redirect or is it possible to proxy in the > > background? > > I'm not sure I think a redirect is good. That would give the user a > > versioned url that he/she might bookmark and then it will be outdated > later > > on. > > I'm a trifle rusty, but I thought that one of the redirect forms in > .htaccess does what you want. But I'm not quite clear on what you > want. Do you want to encourage or discouraged bookmarking the 'latest' > url as opposed to a versioned url? > > If codehaus has the reverse proxy apache mod install we could also use > it as you say, I used to know how to do that. > > > > > > > /Anders > > > > On Wed, May 25, 2011 at 12:22, Benson Margulies <[email protected]> > > wrote: > >> > >> At my day job, we put the versions in the deployment URL. > >> > >> My proposal is then to use .htaccess to map '/foo' to the latest > >> release '/foo/1.2.3'. > >> > >> --------------------------------------------------------------------- > >> To unsubscribe from this list, please visit: > >> > >> http://xircles.codehaus.org/manage_email > >> > >> > > > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
