vy commented on issue #1275:
URL:
https://github.com/apache/logging-log4j2/issues/1275#issuecomment-1757448766
Thanks to hard work of @lukaszspyra in #1753, the situation is improved.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
vy closed issue #1275: Javadoc is broken
URL: https://github.com/apache/logging-log4j2/issues/1275
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
lukaszspyra commented on issue #1275:
URL:
https://github.com/apache/logging-log4j2/issues/1275#issuecomment-1703844557
Hi,
Corrected some javadocs with PR #1753.
There are still many failures remaining, but first need to figure out best
way how to fix links to docs in modules, which
vy commented on issue #1275:
URL:
https://github.com/apache/logging-log4j2/issues/1275#issuecomment-1681235306
I would be in favor of a spotless `javadoc:javadoc` run. Though it all
depends on how far you want to push.
(@lukaszspyra, PMC really appreciates your recent interest and
lukaszspyra commented on issue #1275:
URL:
https://github.com/apache/logging-log4j2/issues/1275#issuecomment-1674335463
Hi,
I have done some checks on modules currently used for HTML javadoc
(according to pom.xml, `log4j-api` and `log4j-core`). Different maven plugin
options for
