commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ceki Gulcu <>
Subject Re: commons-logging version 0.0.0-EMPTY
Date Mon, 18 May 2009 14:14:44 GMT

Matt Benson wrote:

>>> For the actual "source code", see
> Just to point out:  the final location of this "code" should AIUI BE a branch under logging/branches...
the current structure isn't harming anything at the moment, however. 

Sounds good.

 > I think we need to:
 > -agree that the POM is correct/complete according to the wishes of the community
 > -"promote" to proper by moving
 > to
 > -update svn information in POM
 > -generate/tag/vote 0.0.0 RC cycle
 > -release/tag 0.0.0 final

+1  (thank you for making the above list)

Is  there a point in making a standalone release for an artifact which
is empty? For someone using ant there is no point in including
commons-logging.0.0.0-EMPTY.jar, as they can just as easily remove
references to commons-logging in their build.xml file. (Obviously, for
a developer using Maven with *transitive* dependencies, it's a different

Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for Java.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message