On 20/07/2013 17:42, Konstantin Kolinko wrote: > 2013/7/18 Mark Thomas <ma...@apache.org>: >> Given recent progress, I have uploaded a snapshot of the current state >> of trunk to the Maven snapshot repository. Note that our Maven builds >> include full binary distributions (.zip & .tar.gz) so if folks want to >> test the latest Tomcat 8, they can without having to build from svn. >> >> The snapshot repo is here: >> https://repository.apache.org/content/repositories/snapshots/org/apache/tomcat >> >> and the binaries can be found here: >> https://repository.apache.org/content/repositories/snapshots/org/apache/tomcat/tomcat/8.0-SNAPSHOT/ >> >> >> I think we are at the point where we could do a 8.0.0-alpha release. The >> specs (Servlet 3.1, JSP 2.3, EL 3.0, WebSocket 1.0) are all implemented. >> There is still work to do to review the EG disucssions that covered >> various edge cases / things not in the spec to align the implementation >> with what the EG agreed was best practice but didn't make it into the spec. >> >> Any objections to starting the 8.0.0 release process? >> > > What do we do with DBCP? > > a) There will be a new release in Apache Commons
That requires a pool 2.0 release and then a dbcp 2.0 release. > b) Require "patch" tool as prerequisite > (It needs to be explicitly installed and configured on Windows) > https://issues.apache.org/bugzilla/show_bug.cgi?id=54522 > > c) Make DBCP optional, e.g. introduce "skip.dbcp" property like > existing "skip.installer" one. > > d) Drop DBCP pool > > I am currently using a variant of "c)" by setting "no.build.dbcp=true" > (thus fooling an up-to-date check), but an explicit and documented > property would be better. e) ship a dbcp version built from svn rather than a release. My own preferences (in order) are: a, e, b, c, d I'll see what I can do to towards a. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
