DO NOT REPLY [Bug 8519] New: - Port inserted in redirect

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Request for more events to the LifeCycle Re: [VOTE] Release Plan for Apache Tomcat 4.1

I've not accessed the latest Catalina source since 4.0.1, and I can't access this from where I'm working now. I've written a small server that makes use of catalina parts, and as I wrote this server, I wished that LifeCycle had 4 events instead of 2 (Starting, started, stopping, stopped). This le

cvs commit: jakarta-tomcat-site/xdocs/stylesheets project.xml

remm02/04/25 08:00:40 Modified:docs bugreport.html index.html irc.html news.html resources.html xdocs/stylesheets project.xml Log: - Tomcat website update (mentions 4.1). Revision ChangesPath 1.4 +1 -1 jakarta-tom

cvs commit: jakarta-tomcat-4.0 build.xml

remm02/04/25 07:50:10 Modified:.build.xml Log: - Copy the right version of the Jasper source in the source distribution. Revision ChangesPath 1.66 +5 -0 jakarta-tomcat-4.0/build.xml Index: build.xml ===

cvs commit: jakarta-tomcat-4.0/webapps/ROOT index.jsp

remm02/04/25 07:14:29 Modified:webapps/ROOT index.jsp Log: - Automatically fill the version number (defined in the version property). Revision ChangesPath 1.2 +1 -1 jakarta-tomcat-4.0/webapps/ROOT/index.jsp Index: index.jsp =

cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/util ServerInfo.properties

remm02/04/25 07:11:55 Modified:catalina/src/share/org/apache/catalina/util ServerInfo.properties Log: - Automatically fill the version number (defined in the version property). Revision ChangesPath 1.2 +1 -1 jakarta-tomcat-4.0/cata

cvs commit: jakarta-tomcat-4.0/catalina build.xml

remm02/04/25 07:12:07 Modified:catalina build.xml Log: - Automatically fill the version number (defined in the version property). Revision ChangesPath 1.114 +2 -1 jakarta-tomcat-4.0/catalina/build.xml Index: build.xml =

Re: [VOTE] Release Plan for Apache Tomcat 4.1

> Remy Maucherat wrote: > Here is what Craig stated regarding context start/stop events: > - > > > - reload > > > > > > Reloads Context if it is a directory, does not reload if > > > it is running from a war file. A reload does no

DO NOT REPLY [Bug 8436] - Apache httpd 2.0 unable to load Connector : mod_webapp.so

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: Bad build process for mod_webapp for Apache 2

Jean-Frederic - Attached is my libwebapp.la. I think I tried it with libwebapp.so and it did not produce a usable module. However, I am not too experienced a C/C++ programmer and have never used libtool before, so I was winging it. Here is the result of libtool --version: [root@strider weba

Re: [VOTE] Release Plan for Apache Tomcat 4.1

Remy Maucherat wrote: >>Remy Maucherat wrote: >> > >>>The goal of the Apache Tomcat 4.1 final release is to provide a stable >>>container that supports 100% of the mandatory requirements of the >>> > Servlet > >>>2.3 >>>and JSP 1.2 specifications, as well as to improve and add many useful >>>ad

Re: [PROPOSAL] jasper2 detection of compile time page include changes

I also like the idea, however I would like to see some modifications which would allow this idea to work for application development, not only in deployment environments. When developing applications, the requirement is to see the changes immediately, not after a period of time. So there shoul

Re: [PROPOSAL] "New" version numbering scheme

> Do not forget to mention that the dev list MUST be informed in advance of the > release (2 or 3 days and better not on Friday). Ok. So, according to the old release plan, a first milestone (4.1.0, instead of being called 4.1 Beta 1) will be released (tagged) this friday. Since it can be difficu

cvs commit: jakarta-tomcat-4.0 RELEASE-PLAN-4.1.txt

remm02/04/25 01:59:51 Modified:.RELEASE-PLAN-4.1.txt Log: - Update status. - Update with "new" build numbering scheme. Revision ChangesPath 1.5 +9 -9 jakarta-tomcat-4.0/RELEASE-PLAN-4.1.txt Index: RELEASE-PLAN-4.1.txt =

Re: Bad build process for mod_webapp for Apache 2

Jeffrey Bonevich wrote: > (sorry if this has come through already, but I did not see the post on > the mail archive, so I done went and subscribed to the list to resend it) > > > For those of you who do not regularly cruise the tomcat-user postings > (you all do that regularly, right? ;-), a nu

RE: [PROPOSAL] "New" version numbering scheme

>For the uninitiated, the numbering is: >major.minor.build build_stability > >So for example, the first 4.1.x release would probably be numbered: >Apache Tomcat 4.1.0 Alpha > > >[ ] Yes >[ ] No > > >(feel free to provide comments to justify your choice) +1, we have choosen that numbering for mod_

Re: [PROPOSAL] "New" version numbering scheme

Remy Maucherat wrote: >>On Wed, 24 Apr 2002, Ignacio J. Ortega wrote: >> >> De: Remy Maucherat [mailto:[EMAIL PROTECTED]] Enviado el: miércoles 24 de abril de 2002 23:41 >>> >>>Which will be the rules to advance the build numbers? >> >>Probably every time the release manager feels the code

<    1   2