Return-Path: Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 54564 invoked from network); 26 Jul 2000 03:53:48 -0000 Received: from unknown (HELO ?216.216.26.188?) (216.216.26.188) by locus.apache.org with SMTP; 26 Jul 2000 03:53:48 -0000 Received: from no.name.available by [216.216.26.188] via smtpd (for locus.apache.org [63.211.145.10]) with SMTP; 26 Jul 2000 03:56:48 UT Received: from qpdc02.qstrategies.com ([10.10.40.254]) by qserver04.qstrategies.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id PL7ZMRTM; Tue, 25 Jul 2000 20:52:55 -0700 From: "Christian Nichols" To: Received: from ppp-207-214-176-1.anhm01.pacbell.net ([207.214.176.1]) by qpdc02.qstrategies.com via smtpd (for [10.10.40.5]) with SMTP; 26 Jul 2000 03:56:46 UT Subject: RE: Why Properties became immutable Date: Tue, 25 Jul 2000 20:55:26 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 In-Reply-To: Importance: Normal X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N setup targets using the javac with the "includes" attribute to include just those packages that you want for each one. Do the same for the jar's. I have done this very same thing with our project based on packages since we tend to work on a single package at a time, but want to have a single build system for all packages. This let us define targets for each package for the code/debug cycle, but the "core" target depends on all of these to build the entire project. Here is a sample build.xml c. -----Original Message----- From: David Walend [mailto:dwalend@eecs.tufts.edu] Sent: Tuesday, July 25, 2000 8:42 PM To: ant-dev@jakarta.apache.org Subject: Re: Why Properties became immutable On Tue, 25 Jul 2000, James Duncan Davidson wrote: > on 7/25/00 7:18 AM, Stefan Bodewig at bodewig@bost.de wrote: > > > Actually already is at the same level as . I now > > regret we didn't take the full swing to forbid placing them inside of > > targets. > > Here's a vote for doing exactly that... properties belong as project > children only. I have what I think is a dumb newbie question. I have no doubt this thread is over my head. I have a source tree with client code, server code, and common code intermangled. I'd like to set up ant to just build the .jars for the server, or just build the .jars for the client. My gut take on how to do this was: set up server-jars and client-jars targets, each of which sets properties for generic classes (calls javac) and jars (calls jar) targets. But this won't work due to immutable properties. What's a good approach to solve this problem in ant? Thanks, Dave