Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 83515 invoked from network); 9 Feb 2002 18:10:28 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 9 Feb 2002 18:10:28 -0000 Received: (qmail 13932 invoked by uid 97); 9 Feb 2002 18:10:28 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 13916 invoked by uid 97); 9 Feb 2002 18:10:28 -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 13905 invoked from network); 9 Feb 2002 18:10:27 -0000 Message-ID: <015c01c1b195$133972a0$d1eefea9@homenkf0y0hwu0> Reply-To: "Stephane Bailliez" From: "Stephane Bailliez" To: "Ant Developers List" References: <3C66134B.9040502@apache.org> Subject: Re: [PATCH] Path creation with elements specifed in an external file Date: Sat, 9 Feb 2002 19:10:34 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ----- Original Message ----- From: "Jason van Zyl" Hi Jason, nice to see you around :-) > -> Localize JAR dependencies to a single location. Right now this is a > simple text file that I generate from the Gump project descriptors but > eventually I would like to use the project descriptors in a more direct > way. Same. What I have at work is a system similar to yours but less elaborated. I have a lib.properties that is included by each project in its build file. and that gives property names to third party. so that no one really knows where are the thirdparty but the basedir, something like: and in the lib.properties: xalan.jar=${lib.dir}/xalan/xalanj/xalan2/lib/xaland11..jar so that no ones know what is the real name and location of xalan, it makes it very easy to upgrade it, all I have to do is change the lib.properties people won't notice in the next label. I have a gump descriptor per third party or project in its directory (previously it was set up in a central place like Sam does but it does not work well since we have to maintain both buildfile and gump descriptor in different places and it is a pain to label each of them.) However the system I have does not manage dependencies and is maintain by hand so I duplicate the path in the lib.properties and gump.xml descriptor, I thought about generating the lib.properties, so I'm glad you're into it :-) > id="classpath" > dir="${lib.repo}" > pathlist="deps.list" > /> mm.. I understand your point but the couple dir/pathlist is bothering me a little bit, but I guess we don't have much choice. I would not like people to confuse 'dir' with a directory path as with 'location' And it has to be available in a pathelement too, something like: basedir being optional and overriding the project basedir to resolve files. but again I have to use a 'file' name...damn, confusing. maybe 'pathlistfile', or creating a new element for these kind of use, I'm curious to see how we can a path to plug gump descriptors directly and we probably have to think about that or use a new datatype Thoughts ? Stephane -- To unsubscribe, e-mail: For additional commands, e-mail: