Fwd: Re: [PROPOSAL] archive old unmirrored tomcat releases
those who prepare release notes in the future might find this useful. the urls in the release documents should now redirect to jakarta.apache.org/site/binindex.cgi so hopefully the user should be able to find the release from there. Begin forwarded message: From: Stefan Lasiewski [EMAIL PROTECTED] Date: Fri Sep 05, 2003 08:45:11 PM Europe/London To: [EMAIL PROTECTED] Subject: Re:[PROPOSAL] archive old unmirrored tomcat releases Hi Robert, I'm not a tomcat developer, but I saw your message on the tomcat-dev archive page. I know of another reason why so many people are downloading 4.1.24 instead of 4.1.27. The README on the webpage (http://jakarta.apache.org/tomcat/tomcat-4.1-doc/README.txt) is a little confusing, but it suggests that we look in http://jakarta.apache.org/builds/jakarta-tomcat-4.0 for updates. If you look under there, the latest version is 4.1.24. In fact, http://jakarta.apache.org/tomcat/tomcat-4.1-doc/index.html makes no reference to the correct download location. I glossed over the link at There are numerous other links telling folks to go to http://jakarta.apache.org/builds/jakarta-tomcat-4.0 instead of the correct download location. I opened a bug to track this: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22823 As a new user to Tomcat, I found this a little confusing. Thanks for all your hard work, I've been an Apache HTTP user for 4 years, and am very excited in having an opportunity to work with Tomcat here. A few of us are pushing hard. Next, Struts! -= Stefan Stefan Lasiewski, Release Engineer Innovative Interfaces, Inc. - QA Department 510-450-6363 ext. 4209 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
does tomcat have a nominated contact for security issues?
does tomcat have a nominated contact for security issues? (those people who are pmc members will probably already know why i'm asking) - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: does tomcat have a nominated contact for security issues?
On Monday, September 8, 2003, at 08:43 PM, Remy Maucherat wrote: robert burrell donkin wrote: does tomcat have a nominated contact for security issues? (those people who are pmc members will probably already know why i'm asking) Security issues should be forwarded to the tomcat-committers list. it looks like security will always forward first to the pmc. someone who's on both lists needs to forward. does anyone remember something a while ago about the ASF asking for a nominated individual from each (sub?) project to sit on security at apache? (or did i just imagine it...) - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] archive old unmirrored tomcat releases
On Thursday, September 4, 2003, at 07:34 AM, Stefan Bodewig wrote: On Wed, 3 Sep 2003, robert burrell donkin [EMAIL PROTECTED] wrote: snip 1. all available distributables for the latest tomcat 3, tomcat 4 and tomcat 5 releases be added to the appropriate mirrored directories and linked to jakarta download pages. Only the latest stable releases, I'd say. i've add the latest tomcat 3 release (3.3.1a). Please also note the conversation between myself and Glenn in another thread about the connector releases. i've left the connectors alone. 2. the older releases for tomcat 3, tomcat 4 and tomcat 5 be moved into the ASF archives this shouldn't include betas/alphas/milestones either IMHO. 3. move betas/alphas/milestones to http://cvs.apache.org/dist/jakarta/. I'm not sure whether there is any point in keeping unstable releases that have been superseded by newer releases around at all. Just MHO. i couldn't see very many betas or milestones. i've moved all the releases into archive and i've added .htaccess file which redirect to the main jakarta download page. - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[PROPOSAL] archive old unmirrored tomcat releases
(as many you will know) the apache software foundation policy concerning releases is now that all releases should be available only through: 1. the main mirrored ASF distribution directories 2. the main ASF archives tomcat releases are still available through the older unmirrored directories. the download statistics (supply by infrastructure) show that unmirrored tomcat downloads from these directories are still proving far too popular. this is a major issue since the ASF has to pay for bandwidth. my proposal is that: 1. all available distributables for the latest tomcat 3, tomcat 4 and tomcat 5 releases be added to the appropriate mirrored directories and linked to jakarta download pages. if necessary, md5's and signatures will be created for these distributables. (except for tomcat 3 this should just be checking and tidying up). 2. the older releases for tomcat 3, tomcat 4 and tomcat 5 be moved into the ASF archives (where they will remain available for download) and that all requests be redirected to the main jakarta binary download page where the latest release can be downloaded or the link to the archives can be followed. (unless someone else steps forward) i'll volunteer to carry out this work. (unless someone corrects me) i'll assume that the decision will proceed by lazy consensus. (unless someone forces a vote before then) i'll carry out this work sometime after 12 noon GMT on this friday (5th september). - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[PATCH] org.apache.catalina.core.ApplicationContext toString()
this patch adds a toString() method to
org.apache.catalina.core.ApplicationContext.
why does ApplicationContext need a toString() method? so that logging
code can print out something meaningful when the context is passed in!
BTW i'm not currently subscribed to tomcat-dev so any communication
needs to be directed to my account (rather than the list).
- robert
Index: catalina/src/share/org/apache/catalina/core/ApplicationContext.java
===
RCS file:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/ApplicationContext.java,v
retrieving revision 1.19
diff -u -r1.19 ApplicationContext.java
--- catalina/src/share/org/apache/catalina/core/ApplicationContext.java 2001/04/06
19:31:17 1.19
+++ catalina/src/share/org/apache/catalina/core/ApplicationContext.java 2001/04/21
+12:25:52
@@ -837,6 +837,21 @@
}
+/**
+* Returns something meaningful.
+* This returns "Servlet Context " + the display name + "(" + the context name +
+")".
+* Useful for logging.
+*/
+public String toString()
+{
+String ret="Servlet Context ";
+if (getServletContextName()!=null)
+{
+ret += getServletContextName();
+}
+
+return ret + " (" + context.getName() + ") ";
+}
// Private Methods
[PATCH] stopping catalina without DNS lookup
hi!
(i'm not subscribed to this list so please direct any questions to my
home email address)
stopping catalina requires a name lookup since it request localhost by
name.
(i'm pretty that this why i couldn't stop tomcat after my domain name
server became stuffed - which is, of course, a very good reason why one
would wish to shutdown tomcat ;-)
this patch replaces "localhost" name with the IP address ("127.0.0.1")
in the stop method of org.apache.catalina.startup.Catalina. it's a one
line change (in fact, one word) but i haven't set up CVS on the patch
machine and got the latest version from CVS so i hope it's ok. also
hopefully the attached patch will come through ok without becoming
garbled.
- robert
--- Catalina.java.old Sun Jan 28 13:59:22 2001
+++ Catalina.java Sun Jan 28 09:00:25 2001
@@ -701,7 +701,7 @@
// Stop the existing server
try {
- Socket socket = new Socket("localhost", server.getPort());
+ Socket socket = new Socket("127.0.0.1", server.getPort());
OutputStream stream = socket.getOutputStream();
String shutdown = server.getShutdown();
for (int i = 0; i shutdown.length(); i++)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
