Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 26626 invoked from network); 24 Jan 2003 12:50:14 -0000 Received: from exchange.sun.com (192.18.33.10) by 208.185.179.12.available.above.net with SMTP; 24 Jan 2003 12:50:14 -0000 Received: (qmail 9920 invoked by uid 97); 24 Jan 2003 12:51:34 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 9870 invoked by uid 97); 24 Jan 2003 12:51:33 -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 9858 invoked by uid 98); 24 Jan 2003 12:51:32 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) content-class: urn:content-classes:message Subject: RE: Import basedir MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Fri, 24 Jan 2003 12:50:05 -0000 Message-ID: <747F247264ECE34CA60E323FEF0CCC0C0F50B2@london.cellectivity.com> X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Import basedir Thread-Index: AcLCRLgyVf1GjMy4TxekVFXc6yijwQBYKQFw From: "Jose Alberto Fernandez" To: "Ant Developers List" X-Spam-Rating: 208.185.179.12.available.above.net 1.6.2 0/1000/N X-Spam-Rating: 208.185.179.12.available.above.net 1.6.2 0/1000/N > From: Costin Manolache [mailto:cmanolache@yahoo.com] >=20 > I don't know if a conclusion has been reached - but=20 > I think it is clear that we need a way to support the various > options - regardless of what default is chosen. >=20 fine. > The best solution ( IMO ) is to associate each UnknownElement > with a Source - the file ( or URL, InputSource, etc ) that was > used to read it. The source will be a lightweight Project - with > basedir, name, file, etc. >=20 > Resolving relative paths will be based on the Source or Project- > based on some policy.=20 >=20 OK. > The real problem IMO is the overloading of basedir - too many > options.=20 >=20 > There are 2 intuitive behaviors:=20 > - resolve a relative path based on the file where it was included > - resolve it based on some base dir ( like PWD on unix ). > I would suggest refracing the above 2 options: - resolve a relative path based on the basedir of the file where it was = included - resolve it based on some other base dir (like PWD on unix). =20 > Since most ant files are currently using the build file as=20 > base - I think > that must be the default, with explicit overrides permitted. >=20 I.e., Ant files currently use a basedir of "." which is relative to the = buildfile, this is the default for the basedir attribute on . But if we have all current buildfiles expect to = go to use the parent directory. > Disambiguating is another solution - just use a separate property > to describe the "top" file, and use it explicitly in files written > specifically for import ( like fragments ).=20 >=20 If we doit this way then we can deal with the issue of using the = importer basedir by just allowing something like: > I can start working on an impl this weekend - unless someone else > wants to do it or a different solution is proposed. >=20 > Costin=20 >=20 Jose Alberto >=20 > -- > To unsubscribe, e-mail: =20 > > For additional commands, e-mail:=20 > >=20 >=20 -- To unsubscribe, e-mail: For additional commands, e-mail: