Hi all, I think one of the main problems preventing Log4j API from being used more wildly are naming problems and misinformation on many sites.
Personally I find the name `log4j-core` for our implementation quite unfortunate: this is often interpreted as "core Log4j classes", which suggests that all artifacts including `log4j-api` should be considered as a unit. I would profit from the major version bump to change it to `log4j-impl` or `log4j-runtime`. Similar changes have occurred in other projects. For example JAXB changed it's implementation from `jaxb-impl`[1] to `jaxb-runtime`[2] (and also the group id), during the jakartification process. The Java EE Mail project used `javax.mail-api` for their API and `javax.mail` for their implementation. Now they renamed their implementation to `angus-mail`, which stresses the difference between API and implementation more (although in this case Angus **is** the only implementation available). So, what do you think about renaming `log4j-core`? Piotr [1] https://mvnrepository.com/artifact/com.sun.xml.bind/jaxb-impl [2] https://mvnrepository.com/artifact/org.glassfish.jaxb/jaxb-runtime [3] https://mvnrepository.com/artifact/javax.mail/javax.mail-api [4] https://mvnrepository.com/artifact/com.sun.mail/javax.mail [5] https://mvnrepository.com/artifact/org.eclipse.angus/angus-mail
