From ant-dev-return-41317-qmlist-jakarta-archive-ant-dev=jakarta.apache.org@jakarta.apache.org Fri Jan 17 15:02:49 2003 Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 32413 invoked from network); 17 Jan 2003 15:02:48 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 17 Jan 2003 15:02:48 -0000 Received: (qmail 14381 invoked by uid 97); 17 Jan 2003 13:55:15 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 10486 invoked by uid 97); 17 Jan 2003 13:53:37 -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 28961 invoked by uid 98); 17 Jan 2003 13:47:48 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <3E270A09.2050801@ct42.de> Date: Thu, 16 Jan 2003 20:37:45 +0100 From: Claas Thiele User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ant Developers List Subject: Re: Import use cases, basedir behavior and target, property prefixing References: <3E2494BF.8060803@ct42.de> <3E24A5F6.20009@chalko.com> <3E25BE98.1040001@ct42.de> <3E25C5EE.3070106@chalko.com> Content-Type: text/plain; charset=us-ascii; format=flowed 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 Nick Chalko wrote: > Claas Thiele wrote: > >> Costin Manolache wrote: >> >>> Nick Chalko wrote: >>> >>> >>> >>>>> (2) linking subprojects in a large project >>>>> >>>>> >>>> >>>> >>>> I do not think (2) is a usecase for import. I think it is better >>>> handled by the "ant" task. >>>> >>> >>> >>> >>> I think (2) is an important usecase - at least for me. >>> >>> If you use import, you can call any target you want from any >>> of the build files, reuse fragments and targets >>> from other build files, etc. >>> >>> >> Possible disadvantages of use: >> - cannot span dependencies to 'imported' targets >> - cannot access properties and data (i.e. xmlcatalogs, ...) of >> 'imported' files >> >> Example for missing dependecy feature: >> >> Assuming some subprojects. Each subproject uses a common library to >> be build before building the subproject. >> Calling the subprojects from main project via activates the >> build of common lib for each subproject even it is not nessesary. > > > I would leave inter project depenencies to Gump, or some other tool. > > I think use case 2 complicates import with providing enough to really > handle what users want out of use case 2. On second thought I agree. Claas Thiele -- To unsubscribe, e-mail: For additional commands, e-mail: