Return-Path: Delivered-To: apmail-jakarta-avalon-phoenix-dev-archive@apache.org Received: (qmail 19838 invoked from network); 9 Oct 2002 21:28:08 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 9 Oct 2002 21:28:08 -0000 Received: (qmail 923 invoked by uid 97); 9 Oct 2002 21:28:58 -0000 Delivered-To: qmlist-jakarta-archive-avalon-phoenix-dev@jakarta.apache.org Received: (qmail 879 invoked by uid 97); 9 Oct 2002 21:28:57 -0000 Mailing-List: contact avalon-phoenix-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon-Phoenix Developers List" Reply-To: "Avalon-Phoenix Developers List" Delivered-To: mailing list avalon-phoenix-dev@jakarta.apache.org Received: (qmail 853 invoked by uid 98); 9 Oct 2002 21:28:56 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <3DA49F3E.4010308@yahoo.com> Date: Wed, 09 Oct 2002 22:27:26 +0100 From: Paul Hammant User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Avalon-Phoenix Developers List CC: Avalon Applications Developers List Subject: Phoenix 4.0.1 preview release Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Folks, http://jakarta.apache.org/builds/jakarta-avalon-phoenix/nightly/2002-10-09/ It includes .. * better logging and backwards compatability * An updated MX4J (actually from their CVS HEAD) with serious bugs fixed. * Actual delete of the contents of the work/ directory on start. * Wrapper 2.2.8 (Windows only) for thunking into the Windows services panel. This is compatible with all the usual SAR files including the incredibly exiting Catalina SAR (Sevak-Catalina from Daniel K). When the MX4J team release 1.1.1, we'll do the same for 4.0.1 formally. This URL is for those that want to see the changes now and can't wait a few days. I've not uploaded the source as the build.xml will try to get the MX4J 1.1 release which is no longer compatible. I have also not committed the changed build.xml for the same reason, unless people are willing to make some manual jar replacements after the 'get-mx4j' target. Maybe if we can be brave with the inclusion of the MX4J jars, I could date suffix them as we do with other jars. We don't as we are unsure that the MX4J project is correctly licensing the javax.management classes. At least that is why I think we are not uploading the jars to CVS.... Regards, - Paul -- To unsubscribe, e-mail: For additional commands, e-mail: