I would try the following approach: (1) write the value to a file and (2)
import the file back to the Ant script.
Perhaps something like this.
bar.as
baz.as
...
The might need to be included in the
--glenn
On Thu, Jul 16, 2009 at 15:56, HamletDRC wrote:
>
> Hi,
>
> Is it possible
Hello,
I'm trying to clean up our build process, and one of the problems is
that everyone on the team uses a different configuration mechanism
(environment vars, properties files, manual config,...). In trying to
be backwards compatible with everyone's process I find I would like a
task that
Hi,
Is it possible to do this?
I have a property that contains two XML elements as a String:
And I want it expanded into the execution of a task as if I wrote this:
bar.as
baz.as
I expected this to work:
${foo}
But I get the error:
The
I am not aware of the task being able to use the output
parameter property. It's certainly isn't documented. However, if it works,
it works.
The issues are still the same. You now are dependent on both Ant and the
AntContrib tasks. Many people install Ant, but fewer have the AntContrib
package in
On 2009-07-16, Scot P. Floess wrote:
> Wasn't this covered/solved yesterday on the mailing list?
> On Wed, 15 Jul 2009, manish.s...@wellsfargo.com wrote:
>> I am having this weird issue which has me stumped and don't know
>> where to look further.
I think Manish posted the question a second ti
Wasn't this covered/solved yesterday on the mailing list?
On Wed, 15 Jul 2009, manish.s...@wellsfargo.com wrote:
Hi,
I am having this weird issue which has me stumped and don't know where to look
further.
It's the standard task and I have a fileset.
