Return-Path: Delivered-To: apmail-jakarta-jetspeed-dev-archive@apache.org Received: (qmail 91668 invoked from network); 4 Jan 2002 21:27:07 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 4 Jan 2002 21:27:07 -0000 Received: (qmail 15936 invoked by uid 97); 4 Jan 2002 21:27:08 -0000 Delivered-To: qmlist-jakarta-archive-jetspeed-dev@jakarta.apache.org Received: (qmail 15920 invoked by uid 97); 4 Jan 2002 21:27:07 -0000 Mailing-List: contact jetspeed-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jetspeed Developers List" Reply-To: "Jetspeed Developers List" Delivered-To: mailing list jetspeed-dev@jakarta.apache.org Received: (qmail 15909 invoked from network); 4 Jan 2002 21:27:07 -0000 Message-ID: <3C361DD7.4070207@apache.org> Date: Fri, 04 Jan 2002 16:25:43 -0500 User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1 X-Accept-Language: en-us, es, de MIME-Version: 1.0 Subject: Re: Updating the Turbine jar file References: <3C35F771.20306@apache.org> <009501c19558$0d655550$86e5c53f@netfish.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit To: Jetspeed Developers List From: Paul Spencer X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N David, David Sean Taylor wrote: > Could you explain what exactly is the problem. > o Need to get number of cached objects. This will display the number of cached objects in the GlobalAdminPortlet. This patch has already been committed. See http://www.mail-archive.com/turbine-dev%40jakarta.apache.org/msg04799.html o Need to set the expiration of a cached object. I am wait on this patch. See http://www.mail-archive.com/turbine-user%40jakarta.apache.org/msg05525.html > But yes, I don't think its a problem to upgrade the turbine jar, just make > sure that you don't break anything. It would be nice if we had some kind of > unit or smoke tests in place for this situation.... > > Yes, we do need to define some testing. Their are some build_test_xxx.xml files in the build directory. This leads me to believe that automated testing was setup at one time. If this was working, would it fulfill the testing requirement? Paul Spencer -- To unsubscribe, e-mail: For additional commands, e-mail: