tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Barker" <wbar...@wilshire.com>
Subject Re: Apache 2.1.3 may be beta...
Date Tue, 08 Mar 2005 03:28:05 GMT

----- Original Message ----- 
From: "William A. Rowe, Jr." <wrowe@rowe-clan.net>
To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Sent: Monday, March 07, 2005 5:55 PM
Subject: Re: Apache 2.1.3 may be beta...


> At 01:01 PM 3/7/2005, Mladen Turk wrote:
>>Bill Barker wrote:
>>>>
>>>>It seems Apache 2.1.3 may became beta, what about the state of ajp
>>>>code present in CVS ?
>>>Well, Gump is still failing to build mod_jk against Apache 2.1.x-dev ;-).
>>
>>Yep, look at the thread at httpd-dev about making 2.1.3 as beta.
>>First, WIN32 build can not be made because APR build is broken,
>>so you'll need to use the version from CVS.
>
> For what it's worth, there were issues in both httpd and apr, and
> cvs HEAD of both should solve them.  Hopefully both will be picked
> up in a 2.1.4 before it goes beta.
>
> I've seen nothing at dev@httpd about gump build failures, it would
> be nice if folks would forward details about problems that the
> community is unaware of.
>

Actually, it's in the [STATUS] that Rodent sends to dev@httpd periodically. 
You can also see the problem at:
http://issues.apache.org/bugzilla/show_bug.cgi?id=32787

>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>
>
> 



This message is intended only for the use of the person(s) listed above as the intended recipient(s),
and may contain information that is PRIVILEGED and CONFIDENTIAL.  If you are not an intended
recipient, you may not read, copy, or distribute this message or any attachment. If you received
this communication in error, please notify us immediately by e-mail and then delete all copies
of this message and any attachments.

In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet
is not secure. Do not send confidential or sensitive information, such as social security
numbers, account numbers, personal identification numbers and passwords, to us via ordinary
(unencrypted) e-mail.



Mime
View raw message