Here is the use case: I'm working on an Extension Manager which scan all the jars in the classpath to know what is already there and should not be installed again as dependency of some extension. For this a scanner is un at startup to find maven properties in jars to know what they are, it's correctly finding log4j-over-slf4j but it does not find log4j of course which mean that as soon as someone is trying to install some jar that depends on log4j it will install it which is not great.

One solution for this (and what I'm doing in a custom jar but I don't like custom ) is to make the jar give information about the fact that it can also be used as log4j.