Return-Path: Mailing-List: contact general-help@xml.apache.org; run by ezmlm Delivered-To: mailing list general@xml.apache.org Received: (qmail 52230 invoked from network); 7 Jan 2000 13:42:15 -0000 Received: from lotus2.lotus.com (192.233.136.8) by 63.211.145.10 with SMTP; 7 Jan 2000 13:42:15 -0000 Received: from internet2.lotus.com (internet2 [9.95.4.236]) by lotus2.lotus.com (8.9.3/8.9.3) with ESMTP id IAA01165 for ; Fri, 7 Jan 2000 08:55:26 -0500 (EST) From: Shane_Curcuru@lotus.com Received: from cammail01 (CAMMAIL01.lotus.com [9.95.5.59]) by internet2.lotus.com (8.9.3/8.9.3) with ESMTP id IAA21820 for ; Fri, 7 Jan 2000 08:38:12 -0500 (EST) Subject: Re: $Log$, and general Q? on compilers To: general@xml.apache.org X-Mailer: Lotus Notes Release 5.0.2a November 23, 1999 Message-ID: Date: Fri, 7 Jan 2000 08:45:04 -0500 X-MIMETrack: Serialize by Router on CAMMAIL01/CAM/M/Lotus(Release 5.0.2b |December 16, 1999) at 01/07/2000 08:45:06 AM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii A couple of questions for any Java-based projects about suggested guidelines: -- Which Java compiler(s) should we generally use for - in particular for regular binary releases in projects like Xalan, Xerces, etc.? Obviously most 'developers' will probably recompile on their own, but for 'users' it would be nice to have releases ready to run in whatever environment they're most likely to use. I was thinking the obvious choices would be Sun's JDK 1.1.8 or 1.2.2. -- (a per-project issue) What source-control tags should we use in sources? Personally I'd vote for including just $Id$ in a set place (top of first comment?) in every file, and not using any other tags. However a number of other developers don't like using this when they're doing diffs for some reason. ---- Arnaud Le Hors wrote: ---- > May I request that people get rid of the RCS/CVS logs in their source > files? I find that particularly annoying and would suggest we only put > $Id$. Oh, and yes, we're working on making a Xalan-J 0.19.2 release today (hopefully) compiling against the posted Xerces-J 1.0.1 release, so that should clear up the compiler issues. I plan to use the existing makefiles for this build, and hope to get an Ant build, at least for the compile, samples, and jarring, for the next release. ---- ---- - Shane Automation, Test, & Build guy mailto:shane_curcuru@lotus.com AIM:xsltest http://alphaworks.ibm.com/tech/LotusXSL http://xml.apache.org/xalan/index.html