While fixing the javadoc for the 2.20.0 release, I renamed the path from
`/<module>/apidocs` to `/javadoc/<module>`. As the user issue below
explains, this got some people angry. I have already temporarily fixed the
issue by creating directory symlinks. For a permanent solution, I see two
options:

   1. Configure the `javadoc-maven-plugin` to output to `/<module>/apidocs`
   instead of `/javadoc/<module>`. The reason I am not happy with this
   approach is that it actually was like that since that is how
   `maven-site-plugin` works and it is not aligned with the website directory
   structure. Nonetheless, it is doable.
   2. Create an `.htaccess` entry *permanently* redirecting
   `2.x/<module>/apidocs` to `2.x/javadoc/<module>`. I am sort of inclined
   with this fix, since we can stick to our directory structure.

Thoughts?

---------- Forwarded message ---------
From: Alexander Brandes <notificati...@github.com>
Date: Wed, Feb 22, 2023 at 9:36 AM
Subject: [apache/logging-log4j2] Broken Javadoc URL (Issue #1284)
To: apache/logging-log4j2 <logging-log...@noreply.github.com>
Cc: Subscribed <subscri...@noreply.github.com>


Hey,

It appears that a recent changed forced a change of the Javadoc URL from
https://logging.apache.org/log4j/2.x/log4j-api/apidocs/ to
https://logging.apache.org/log4j/2.x/javadoc/log4j-api/index.html.

Is there a particular reason why this was changed without a redirect
pointing to the new location? This change affects hundreds
<https://cs.github.com/?scopeName=All+repos&scope=&q=https%3A%2F%2Flogging.apache.org%2Flog4j%2F2.x%2Flog4j-api%2Fapidocs%2F+NOT+lang%3Ahtml>
of files in open source projects, now left behind broken.

Some builds may also fail because a build tool can no longer obtain the
file from the old location:

Error fetching URL:
https://logging.apache.org/log4j/2.x/log4j-api/apidocs/
(java.io.FileNotFoundException:
https://logging.apache.org/log4j/2.x/log4j-api/apidocs/package-list)

—
Reply to this email directly, view it on GitHub
<https://github.com/apache/logging-log4j2/issues/1284>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAARTSI5PVTEJOFKU66PM43WYXFZ3ANCNFSM6AAAAAAVEAR5SA>
.
You are receiving this because you are subscribed to this thread.Message
ID: <apache/logging-log4j2/issues/1...@github.com>

Reply via email to