ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Diane Holt <>
Subject Re: cvs commit: jakarta-ant/src/main/org/apache/tools/ant
Date Mon, 06 Nov 2000 10:22:39 GMT
I was referring to the latest commit -- the one where you made relative
paths for file: be relative to the build-file rather than to basedir. It
seemed like, if we were going to be diddling what the path for file:
resolved to anyway, we might as well add in property-expansion so using
this ENTITY stuff could be (in my opinion) more useful. If I have a bunch
of build-files throughout my tree, and I have a "default.xml" that sets
all the global properties and that I'd like to have included in those
build-files so I don't have to have them all repeat the lines that bring
all those global properties in, then I'd just as soon not have to deal
with something like
since a) that hard-codes in a particular tree-structure, and b) it's
yucky. It'd be much cleaner to just be able to have
file:${workspace}/tools/ant/lib/default.xml, don't you think?

--- Stefan Bodewig <> wrote:
> >>>>> "DH" == Diane Holt <> writes:
>  DH> Would it be possible to not only allow for relative paths, but
>  DH> for absolute paths based on a property (eg.,
>  DH> file:${ant.home}/lib/default.xml)?
> Uhm, which commit are you actually refering to, Diane? Is it the one
> that handles external entity resolution? I read this as "expand
> properties in external entities as well", right?
> Actually I think entity resolution is the parsers job and IMHO both
> parsers (JAXP reference and Xerces-J) have a bug here, that we are
> working around. I'd rather drop that code than expanding on it.
> Stefan


Do You Yahoo!?
Thousands of Stores.  Millions of Products.  All in one Place.

View raw message