Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 50607 invoked from network); 20 Nov 2001 02:37:23 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 20 Nov 2001 02:37:23 -0000 Received: (qmail 9614 invoked by uid 97); 20 Nov 2001 02:37:24 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 9598 invoked by uid 97); 20 Nov 2001 02:37:23 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 9587 invoked from network); 20 Nov 2001 02:37:23 -0000 Date: 20 Nov 2001 02:37:12 -0000 Message-ID: <20011120023712.16712.qmail@mailweb30.rediffmail.com> MIME-Version: 1.0 From: "Magesh Umasankar" Reply-To: "Magesh Umasankar" To: "Ant Developers List" Subject: Re: Smarter Javac Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Tue, 20 Nov 2001 Peter Donald wrote :=0D=0A=0D=0A> I think you missed my= point ;) You have to cache information per-file =0D=0A=0D=0ANope. Didn't= miss it. Was looking at it from Ant 1.x's perspective=0D=0Awhere argument= s other than fileset and classpath are essentially passed=0D=0Aas attribute= s to the task instead of to individual files.=0D=0A=0D=0A> because for some= reason you may always compile file X with debugging, while Y =0D=0A> with = no debugging. This does not mean you can't aggregate the files during =0D= =0A> compiler execution=0D=0A>=0D=0A> javac -g Bar.java Baz.java=0D=0A=0D= =0AHow would a Javac task that takes in 2 compilers, one with debug turned = on, =0D=0Aother turned off, depending upon file being used be setup in buil= d.xml =0D=0Afor Ant 1.x or Ant2? I mean, will current Javac attributes be = set at the =0D=0Afileset level?=0D=0A=0D=0A> That I disagree with ;) There = is sometimes reasons to have different =0D=0A> colorings for different sets= of files. For instance you may need to use a 1.1 =0D=0A> compiler in some = parts of the build and 1.2+ in other parts. Alternatively =0D=0A> you may n= eed to always compile some parts with debug enabled (think testing =0D=0A> = code) while other bits may or may not have debug enabled.=0D=0A=0D=0AConcep= tually agreed. User may want to perform these things. But going back=0D= =0Ato the simple Ant 1.x world that we live in ;-), I run one task with a b= unch =0D=0Aof attributes that may be changed during different runs - these = settings =0D=0Aaffect all files that this task operates upon.=0D=0A=0D=0A> = That is of course unless you want to do the work (and there is a damn lot o= f =0D=0A> it - not an easy bit of coding IMHO), while still being backward = compatible. =0D=0A> If so ... woohooo ! ;)=0D=0A=0D=0A;-)=0D=0A=0D=0AMagesh= =0A -- To unsubscribe, e-mail: For additional commands, e-mail: