Re: Broken Javadoc URL

Fixed this permanently in b1b687be using HTML-based redirects. I have tested it locally, but did not deploy to the website. This will ensure that old links will still work next time somebody generates the web

Re: Broken Javadoc URL

Hi Volkan, On Wed, 22 Feb 2023 at 10:27, Volkan Yazıcı wrote: >1. Configure the `javadoc-maven-plugin` to output to `//apidocs` >instead of `/javadoc/`. 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

Re: Broken Javadoc URL

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: /javad

Re: Broken Javadoc URL

As I said in my earlier email, I am reserving my opinion on this to see if anyone objects to any of the reports that we have eliminated. Personally, I never use them and don’t care that they don’t exist anymore. But if we need to restore one or more reports we will need the subdirectories back a

Re: Broken Javadoc URL

Hi Volkan, On Thu, 23 Feb 2023 at 22:48, Volkan Yazıcı wrote: > 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. If simple web crawlers receive either an HTTP redirect

Re: Reroute Dependabot emails to a separate separate list

I’ve applied the config setting. Let’s see how this works out! > On Feb 17, 2023, at 11:10 AM, Matt Sicker wrote: > > By the way, I found an example config file that customized notification > emails to use subjects that are more commonly supported by email clients to > turn them into threads p

Re: Error while running notifications feature from .asf.yaml in logging-log4j2!

The list has been requested, but it’s not created yet. This will fix itself. > On Feb 24, 2023, at 1:10 AM, Apache Infrastructure > wrote: > > > An error occurred while running notifications feature in .asf.yaml!: > Invalid notification target 'rob...@logging.apache.org'. Must be a valid > @l