Return-Path: Delivered-To: apmail-excalibur-dev-archive@www.apache.org Received: (qmail 69231 invoked from network); 17 Jul 2005 08:00:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 17 Jul 2005 08:00:54 -0000 Received: (qmail 74577 invoked by uid 500); 17 Jul 2005 08:00:53 -0000 Delivered-To: apmail-excalibur-dev-archive@excalibur.apache.org Received: (qmail 74484 invoked by uid 500); 17 Jul 2005 08:00:53 -0000 Mailing-List: contact dev-help@excalibur.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: "Excalibur Developers List" Reply-To: "Excalibur Developers List" Delivered-To: mailing list dev@excalibur.apache.org Received: (qmail 74471 invoked by uid 99); 17 Jul 2005 08:00:52 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 17 Jul 2005 01:00:52 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: unknown (asf.osuosl.org: error in processing during lookup of mail@leosimons.com) Received: from [130.89.168.148] (HELO lsd.student.utwente.nl) (130.89.168.148) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 17 Jul 2005 01:00:48 -0700 Received: from [10.133.196.117] (unknown [80.187.145.105]) (using TLSv1 with cipher DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by lsd.student.utwente.nl (Postfix) with ESMTP id F0A1212F334 for ; Sun, 17 Jul 2005 10:00:05 +0200 (CEST) User-Agent: Microsoft-Entourage/11.1.0.040913 Date: Sun, 17 Jul 2005 10:00:34 +0200 Subject: Re: Excalibur and JDK-1.3 From: Leo Simons To: Excalibur Developers List Message-ID: In-Reply-To: <42D96828.60109@badfw.org> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi shash! On 16-07-2005 22:03, "Shash Chatterjee" wrote: > I am trying to get Excalibur tagged and the RC's released (not going to get > time to do all of it at once, but I'll do as many as I can). Started with > Framework, running into a problem with framework-impl and logkit. > > http://wiki.apache.org/excalibur/ReleaseManagement says to make sure and > compile with JDK-1.3 (I am using Sun jdk-1.3.1_15). Of course, > o.a.a.f.logger.Jdk14Logger does not compile. Similar issues with logkit. > > Are we supposed to overlook this rule? It ain't a rule, its a guideline :-) IIRC compiling for target=1.3 with 1.4 gave us some issues with some little bit of code somewhere at some point, and I think it was Peter Donald who pointed that out; I think this was related to logkit itself (which I believe could actually still compile using 1.2). We've probably got bits of code spread all over the codebase that will only compile against 1.4. I'm not against building jars using 1.4, as long as we ship buildable source distributions so that people that need to can replace particular jars with 1.3-compatible ones that can otherwise be trusted to be the same. IOW, as long as the source distro is of good quality I wouldn't feel too bad about bending a few rules if you need to. Projects like cocoon have long since given up on binary distros, and in fact I know from trying out gump+jdk 1.3 that there's a whole bunch of vital dependencies for most of the apache java projects which you can't compile on a 1.3 jdk out of the box. Its a mess. Don't spend tooooo much time trying to clean it :-) Cheers, Leo --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org For additional commands, e-mail: dev-help@excalibur.apache.org