Chealer opened a new issue, #1475: URL: https://github.com/apache/logging-log4j2/issues/1475
log4j-core [has the following name and description](https://github.com/apache/logging-log4j2/blob/2.x/log4j-core/pom.xml#LL27C1-L28C61): ``` <name>Apache Log4j Core</name> <description>The Apache Log4j Implementation</description> ``` Software products often call a component _core_ when that component is essential to all other components. This pattern can be seen in numerous Debian packages, notably in the nginx source package, which generates binary packages nginx-core and [nginx-full](https://packages.debian.org/bullseye/nginx-full), the latter depending on the former. My understanding is that this is not really the case with Log4j Core, since log4j-api does not _need_ log4j-core, which means its name could be misleading (I believe it did confuse me for one). I would therefore recommend setting a name and a description as clear as possible, focusing on "implementation" rather than "core". I would suggest the following, but this comes from someone who is not knowledgeable about either Log4j or its ecosystem. My suggestion is based on my understanding that "core" means "core of the implementation" but considering that [the API Separation page](https://logging.apache.org/log4j/2.x/manual/api-separation.html) refers repeatedly to the "core implementation", that may be wrong. ``` <name>Apache Log4j Implementation Core</name> <description>Core of Apache Log4j's reference implementation of the Log4j facade API. This implementation provides a full-featured logging library which can also serve as a Simple Logging Facade for Java (SLF4J) provider or as a logging implementation of another logging API.</description> ``` -- 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]
