cvs commit: jakarta-tomcat-connectors/jni/native/src network.c pool.c

mturk 2005/05/28 00:48:29 Modified:jni/java/org/apache/tomcat/jni Pool.java jni/native/src network.c pool.c Log: Add missing userdata functions for Pool. Those will be used for SSL socket abstraction. Revision ChangesPath 1.5 +32 -1

cvs commit: jakarta-tomcat-connectors/jni/native/src jnilib.c

mturk 2005/05/28 01:18:09 Modified:jni/java/org/apache/tomcat/jni Library.java jni/native/src jnilib.c Log: Check if we have at least APR 1.0 and Threading support. Revision ChangesPath 1.6 +10 -2

cvs commit: jakarta-tomcat-connectors/jni/native/include tcn.h

mturk 2005/05/28 01:24:59 Modified:jni/native/include tcn.h Log: Refuse to compile the native if APR_HAS_THREADS is missing. Revision ChangesPath 1.7 +5 -1 jakarta-tomcat-connectors/jni/native/include/tcn.h Index: tcn.h

cvs commit: jakarta-tomcat-connectors/jni/native/include tcn.h

mturk 2005/05/28 01:29:14 Modified:jni/native/include tcn.h Log: Add classpath prefix to easily change the classpath if desired. Revision ChangesPath 1.8 +5 -4 jakarta-tomcat-connectors/jni/native/include/tcn.h Index: tcn.h

DO NOT REPLY [Bug 35113] New: - Possibily to undeploy without removing

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35113. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 35113] - Possibily to undeploy without removing

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35113. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.

cvs commit: jakarta-tomcat-connectors/jni/native/os/win32 system.c

mturk 2005/05/28 04:40:52 Modified:jni/java/org/apache/tomcat/jni OS.java jni/native/os/unix system.c jni/native/os/win32 system.c Log: Update OS info for linux Revision ChangesPath 1.6 +29 -17

cvs commit: jakarta-tomcat-connectors/jni/examples/org/apache/tomcat/jni Echo.java

mturk 2005/05/28 05:13:02 Modified:jni/examples/org/apache/tomcat/jni Echo.java Log: Update examples to conform to API. Add OS.info display. Revision ChangesPath 1.11 +55 -16 jakarta-tomcat-connectors/jni/examples/org/apache/tomcat/jni/Echo.java Index:

DO NOT REPLY [Bug 35113] - Possibily to undeploy without removing

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35113. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.

Re: What to do now

Bill Barker wrote: Now that we are officially a TLP (and, by the way, congrats Remy :), I think it's more congrats Mladen, as he's the one who wanted it most. what is the migration strategy? From the previous discussions: - repositories: remain the same at the moment, in CVS, as we'll have

DO NOT REPLY [Bug 35114] New: - Jasper JSPC does not support a failonerr from Ant

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35114. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.

RE: rfe

Hi, First, please don't cross-post to both tomcat-user and tomcat-dev. I was wondering if any one other than me has had the need to use a run- time 'before-bootstrapping' and 'cleaning-after-at-the-very-end' type of functionality. If I do, there are other places for this that don't require

DO NOT REPLY [Bug 35114] - Jasper JSPC does not support a failonerr from Ant

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35114. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 35114] - Jasper JSPC does not support a failonerr from Ant

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35114. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 35114] - Jasper JSPC does not support a failonerr from Ant

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35114. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 35114] - Jasper JSPC does not support a failonerr from Ant

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35114. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.

Unclear 5.0 release status

Hi, the release status of TC 5.0 is a little unclear: http://jakarta.apache.org/tomcat/tomcat-5.0-doc/status.html states: Tomcat 5.0.29 was released on October 6th, 2004. Work on the 5.0 branch is primarily for maintenance and bug fixes. It is still considered the best branch for production

RE: Unclear 5.0 release status

Hi, the release status of TC 5.0 is a little unclear: http://jakarta.apache.org/tomcat/tomcat-5.0-doc/status.html states: Tomcat 5.0.29 was released on October 6th, 2004. Work on the 5.0 branch is primarily for maintenance and bug fixes. It is still considered the best branch for

Re: What to do now

On Sat, May 28, 2005 at 04:43:45PM +0200, Remy Maucherat wrote: I'm assuming that we'll need to do a new 'ci' on all of what once was jakarta-tomcat*, but did jakarta-servletapi* and jakarta-watchdog* follow us? Does it make more sense to ci all over again, or to move or copy the existing