DBCP is complicated to release, because the source has to be pre-processed in order to build additional versions of the code. (unlike the rest of Java, JDBC is not generally upwards compatible).
The source code in SVN is for the latest JDBC version we support, and can be built and deployed using Maven the same as any other normal Commons component. [At least I assume that is the case; if not that ought to be fixed first] Previous versions are currently built and deployed using Ant which has to pre-process the source before doing the build. Now component RCs should ideally be built from a fresh checkout of the tag, so one possible approach would be to use Ant to create the tag and workspace and then use Maven as before. It would mean using multiple workspaces, but it does not take huge amounts of disk space. The process for previous JDBC versions would be: Checkout a fresh workspace from SVN. Run Ant to fix up the source code Create the RC tag directly from the workspace Use Maven to build and deploy the jars. Does that sound like a possible approach? --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
