The broken URLs are fixed with redirects, doesn't this address your concern?
About "my preferred location"... Let's compare the before-and-after of the new site structure: BEFORE: /log4j-core /log4j-api /log4j-foo /log4j-buzz /log4j-... ... /css /images /fonts /performance.html ... AFTER: /javadoc /css /images /fonts /performance.html ... I think there is clearly an (objective?) improvement here, granted that old URLs still work. If you/others have a different opinion on how shall we structure, I am all ears. On Thu, Feb 23, 2023 at 10:26 PM Piotr P. Karwasz <piotr.karw...@gmail.com> wrote: > Hi Volkan, > > On Wed, 22 Feb 2023 at 10:27, Volkan Yazıcı <vol...@yazi.ci> wrote: > > 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. > > For me URLs are like APIs: we should not break them unless there is a > real need to do it. Whenever I am writing about something I like to > provide a link to the documentation and the Javadoc is a good > documentation for the API. > > Since 3.x will have a Javadoc split by modules, maybe we can switch to > your preferred location in 3.x? > > Piotr >
