The /log4j/2.0/ link is because 2.0 is a symbolic link to 2.x, and 2.x is a symbolic link to the latest release (or at least that’s how it was set up originally). The links can probably use .htaccess rewrite rules instead.
> On Feb 21, 2024, at 04:44, Piotr P. Karwasz <piotr.karw...@gmail.com> wrote: > > Hi, > > On Mon, 19 Feb 2024 at 10:34, Volkan Yazıcı <vol...@yazi.ci > <mailto:vol...@yazi.ci>> wrote: >> >> If there are no objections, after Log4j `2.23.0` and `3.0.0-beta2` >> releases, I want to proceed with replacing the contents of >> `asf-{site,staging}` branches with `clean-staging`. Effectively, this >> operation has the following outcomes: >> >> - The `logging-log4j-site` repository will contain only following files: >> - `1.x` >> - `2.12.x` >> - `2.3.x` >> - `2.x` >> - `3.x` >> - `.asf.yaml` >> - `changelog-*.xsd` >> - `extras` >> - `.htaccess` >> - `.htaccess` will take care of redirections for backward compatibility > > I have replaced `asf-staging` with `clean-staging`, but `asf-site` > remains for now untouched. > > Please peruse the `https://logging.staged.apache.org/log4j/` > <https://logging.staged.apache.org/log4j/%60> pages to > see if something is wrong. > > As I stated before, the main rationale behind this change is SEO. What > do you get if you perform the following search: > > https://www.google.com/search?client=firefox-b-e&q=DefaultThreadContextMap+log4j+javadoc > > The result depends on the location, but I find results from: > > * /log4j/2.0/: (sic!) I didn't even know it existed, can someone tell > me from which repo is this served? > * /log4j/log4j-2.3.2/ > * Eventually there is a result from `/log4j/2.x/` but pointing at the > wrong class. > > Remark: in the renewed staging site there are **still** a > /log4j/2.3.x/ and /log4j/2.12.x/ folders and the rewrite rules > "round-up" the `/log4j/log4j-<version>` folders to one of > /log4j/2.3.x/, `/log4j/2.12.x/` or `/log4j/2.x/`. > We could probably also drop the documentation of those versions too, > but this is another discussion. > > Piotr > > PS: right now INFRA didn't update > https://logging.staged.apache.org/log4j/ yet, but you can see the > intended content on https://logging-clean.staged.apache.org/log4j/
