Return-Path: Delivered-To: apmail-jakarta-ant-user-archive@apache.org Received: (qmail 58049 invoked from network); 2 Dec 2002 22:05:58 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 2 Dec 2002 22:05:58 -0000 Received: (qmail 8914 invoked by uid 97); 2 Dec 2002 22:06:58 -0000 Delivered-To: qmlist-jakarta-archive-ant-user@jakarta.apache.org Received: (qmail 8865 invoked by uid 97); 2 Dec 2002 22:06:57 -0000 Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Users List" Reply-To: "Ant Users List" Delivered-To: mailing list ant-user@jakarta.apache.org Received: (qmail 8853 invoked by uid 98); 2 Dec 2002 22:06:57 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Date: Mon, 2 Dec 2002 16:05:49 -0600 From: Jacob Kjome X-Mailer: The Bat! (v1.54/10) Personal Reply-To: Jacob Kjome Organization: Springfield Nuclear Plant X-Priority: 3 (Normal) Message-Id: <5421374024.20021202160549@visi.com> To: "Ant Users List" Subject: Re[2]: Best practice for numerous javac calls? In-Reply-To: <1654BC972546D31189DA00508B318AC80741ED5D@charmander.wrq.com> References: <1654BC972546D31189DA00508B318AC80741ED5D@charmander.wrq.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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 I have this issue when I use a to call another build file. I specify . I don't specify inheritRefs because it defaults to false. Yet, when I define a custom taskdef in the called file, I get a message saying that I am overriding the a previous definition of a taskdef. I had defined it in the calling build file and ran some stuff, but since I have inheritAll="false" and inheritRefs is false by default, why should it be redefining anything? I can't use any workaround in the called build file that creates a dependency on the calling build file because the called build file must be able to be run directly without reference to the calling build file. Calling the build file using is purely there for convenience and central control over the whole build system. Each build file, however, is meant to be self-sufficient with no dependencies other than common properties file which each build file references. Any solutions to that? Jake Monday, December 02, 2002, 3:48:53 PM, you wrote: SA> Ah, this is what I need: SA> torefid="compile.classpath"/> SA> Thanks Erik! SA> -- Steve SA> // WRQ has 21 years of experience providing integration software and SA> // services for host-intensive environments. To learn more about our SA> // Reflection and Verastream products, visit http://www.wrq.com/products/ >> -----Original Message----- >> From: Erik Hatcher [mailto:jakarta-ant@ehatchersolutions.com] >> Sent: Monday, December 02, 2002 12:13 PM >> To: Ant Users List >> Subject: Re: Best practice for numerous javac calls? >> >> >> I do this very thing in my sample project: >> >> http://www.ehatchersolutions.com/downloads/ >> >> (get the latest version, whatever that happens to be at the time) >> >> Look at my build.xml and how I use . I do not override >> references, I just create a new reference for that particular call. >> >> Erik >> >> >> Steve Allan wrote: >> > Hi, >> > >> > I hava a java project where all the different components >> are under one >> > source root. To accommodate the developers' request to be able to >> > build certain subsections of the code and their dependencies, there >> > are 10 different compile targets. To avoid duplicating all the >> > calls, I wrote a single compile-java target with >> the idea that >> > a component's compile target could define the java source >> and classpath, and >> > then call the java-compile target. Here's a typical example: >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > And the java-compile target looks like this: >> > >> > >> > > > srcdir = "${src.dir}" >> > ... >> > > >> > >> > >> > >> > >> > >> > >> > This works, but if I build all my components in one call to ant, I >> > keep getting messages about redefining references: >> > >> > Overriding previous definition of reference to compile.classpath >> > Overriding previous definition of reference to java.src >> > >> > So I'm wondering >> > >> > 1) Is redefining a reference a 'bad thing'? >> > 2) Is there a better way to achieve this type of granularity in the >> > compile targets? >> > >> > Thanks. >> > >> > -- Steve >> > // WRQ has 21 years of experience providing integration software and >> > // services for host-intensive environments. To learn more about our >> > // Reflection and Verastream products, visit >> http://www.wrq.com/products/ >> > >> > >> > -- >> > To unsubscribe, >> e-mail: >> > For additional commands, e-mail: >> >> > >> > >> > >> >> >> -- >> To >> unsubscribe, e-mail: >> unsubscribe@jakarta.apache.org> >> For >> additional commands, >> e-mail: >> SA> -- SA> To unsubscribe, e-mail: SA> For additional commands, e-mail: -- Best regards, Jacob mailto:hoju@visi.com -- To unsubscribe, e-mail: For additional commands, e-mail: