Yes, I'm aware of that. I'd question the existing groupId/artifactId, too, if only had not it been used for such a long time in its current form.
The same wiki page provides an example which is in the form of a reverse domain name notation. Also, commons-logging is a widely distributed as an OSGI bundle in Eclipse, which wraps it as org.apache.commons.logging (according to http://wiki.eclipse.org/index.php/Naming_Conventions).
Maven conventions (https://maven.apache.org/guides/mini/guide-naming-conventions.html) suggest groupId on a project level (org.apache.commons is listed as an example), so a natural consequence would be naming a jar logging.jar and getting $
resolved to org.apache.commons.logging.
This is of course a very drastic change to the whole community, and I don't want to insist on it (although it would be nice).
I'm, however, using this package in Fedora, and it has been osgified there, and in Eclipse, for a long time, with org.apache.commons.logging id. Current name (commons-logging) is a breaker for me, and I'll have to patch it otherwise.