Ah, Peter, that was it--thanks. I changed my Javascript code to this:
// get ahold of the "war" task in the "buildWar" target
var buildWarTasks = buildWar.getTasks();
var warTask = null;
for (var i = 0; i < buildWarTasks.length; ++i) {
var aTask = buil
Any ideas on this? It's preventing us from upgrading to Ant 1.6, which we
need to do because of other dependencies. Am I doing something horribly
wrong? Any workarounds come to mind?
Thanks.
[EMAIL PROTECTED] wrote on 06/24/2005 10:50:16 AM:
>
> More info:
>
> It's interesting to note that
More info:
It's interesting to note that the output from Ant 1.5.4 shows:
[script]
[EMAIL PROTECTED]
[script] [EMAIL PROTECTED]
...whereas the output from Ant 1.6.2 shows:
[script] reportSet.toString=fileRealm.properties
[script] [EMAIL PROTECTED]
Ant 1.5.4 seems to know what type
I have an Ant 1.5.4 build script that doesn't work in Ant 1.6 (Ant 1.6.2
or 1.6.5). It has some embedded JavaScript that is calling the Ant API to
add a ZipFileSet to the War task.
What we're trying to do is dynamically add directories to the War task at
runtime. We decided to use JavaScript t
