commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Thomas <ma...@apache.org>
Subject Re: [VOTE] Move Apache Commons to Git for SCM...
Date Fri, 11 Oct 2013 07:56:45 GMT
On 11/10/2013 00:41, Olivier Lamy wrote:

<snip/>

> Why other apache projects need to have their own commons-csv
> repackaged release? why tomcat need to use a svn:external on dbcp
> instead of a released version?

Tomcat does not use an svn:external of any Commons component.

Tomcat releases depend only on released versions of DBCP  (excluding the
8.0.x release candidates which are using snapshots of Pool 2 and DBCP 2
and will switch to released versions before the first stable 8.0.x
release) .

Tomcat does have package renamed versions of Pool, DBCP, Digester,
Logging, FileUpload, Codec and BCEL. Some of these are via svn cp, some
(including DBCP) are scripted from the released source tarballs.

Tomcat depends directly on Daemon.

There are several reasons why Tomcat does not, can not and will not ship
Commons JARs directly:
- the package rename is necessary to avoid potential conflicts if a web
application ships with the same jar
- sometimes Tomcat only needs a few classes from a much larger JAR

None of the reasons have anything to do with Commons's choice of git vs
svn, Ant vs Maven or the frequency of releases.

There is nothing that Commons's could do that would remove the need for
Tomcat to repackage these JARS and enable Tomcat to simply ship the
released JARs directly.

There is nothing that Commons's could do to make it easier for Tomcat to
consume these artefacts (if there was, I'd have done it already).

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message