Matt Benson wrote:
For the actual "source code", see
https://svn.apache.org/viewvc/commons/sandbox/logging_empty/trunk/
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
> https://svn.apache.org/repos/asf/commons/sandbox/logging_empty/trunk
> to
> https://svn.apache.org/repos/asf/commons/proper/logging/branches/logging_EMPTY
> -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
matter.)
--
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
