Craig L Russell wrote:
Just for my information, why is it not desirable to package this as an OSGi compliant jar?
Because we would not want an empty bundle containing no classes to usurp the place of the real commons-logging OSGi bundle.
Also, why is the maven group id commons-logging and not org.apache.commons? Is this just a historical curiosity or was there a purpose?
The artifact we want substitute for has the groupId "commons-logging". Version 0.0-EMPTY has to have the exact same groupId, otherwise it would not be a Maven dependency substitute.
Thanks, Craig
-- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
