vy commented on issue #4015: URL: https://github.com/apache/logging-log4j2/issues/4015#issuecomment-3764268072
> Regarding the artifact, I'm planning to use `log4j-message-masking` as the ArtifactId. This is tricky. I'd avoid using `masking` in the Artifact ID — users can use your Message Rewrite Policy for various goals, not just for masking. I'd recommend `log4j-utils`, `log4j-extras`, etc. — something generic enough to hold your future Log4j plugins. > For the GroupId, would you recommend I use my GitHub namespace (e.g., io.github.neel1210) or is there a different convention you'd prefer for 3rd-party plugins referenced in the docs? We don't have a convention and it does not matter for us. What I'd _personally_ recommend you is the following: if you own a domain name yourself (e.g., `neeleshmehar.com`), use that one (i.e., `com.neeleshmehar`) for the Group ID. This will be the most future-proof solution for you. If you ever decide to move away from GitHub to elsewhere (GitLab, Codeberg, etc.) this won't disrupt your packages' Maven coordinates. > I'll get started on setting up the repository and the Maven Central publishing process. I’ll keep you posted once the artifact is available so we can proceed with the documentation PR. @Neel1210, awesome! Keep us posted! Good luck! -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
