ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Duncan Davidson <james.david...@eng.sun.com>
Subject Re: A question about "available" and doing conditionals in a build xml file.
Date Sun, 18 Jun 2000 08:15:00 GMT
on 5/18/00 2:18 AM, Stefan Bodewig at bodewig@bost.de wrote:

> The responses I did get boiled down to "we agree that properties are
> confusing, that there should be some changes and that we don't want to
> make Ant a new programming language".
> 
> Let me address the first two points separately.
> 
> "properties are confusing":
> 
> The property tasks are evaluated in the same order they appear inside
> the XML-File. It doesn't matter whether they are inside targets or not -
> they are executed by the parser before anything else happens.

Nit: properties aren't tasks -- they are just XML tags that happen...

> The main changes are that tasks get instantiated at runtime, just
> before they are actually executed, and are expected to access
> properties through the project. Note there is no mention of the ${}
> construct at all.

Yes, the ${} need to die die die and go away. Or at least the way that they
behaive today.

> Most (all?) people involved agree that some way of conditional
> compilation - or more generally conditional task execution - is
> needed, but there are different opinions about how to do this.

I still think that conditional compilation can be handled inside the javac
task. :)


.duncan


Mime
View raw message