I would run ant -debug so you can see exactly how the properties are
being set and what the resulting exec command is.
I'm assuming that you're invoking ant something like this:
ant -Dsome.path=/some/path -Dsome.value=some_value
Correct?
Ruby John wrote:
>
> I am trying to integrate ant with our proprietary tools which I intend to
> call from the ant build.xml.
> I want to specify the work areas to create for fetching source and building
> as command line arguments to ant.
> The program that I am <exec>uting is complaining about the invalid
> character: "{" which it should not be seeing.
>
> I am a brand new user so I may not be doing something basic.
>
> "Larry V. Streepy, Jr." wrote:
>
> > If you're defining both some.path and some.value using -D flags to ant,
> > then what you wrote should work fine. Can you be a little more detailed
> > on what you want to accomplish?
> >
> > Ruby John wrote:
> > >
> > > How do I get property or path variables to be expanded when passing
> > > arguments to a <exec> task?
> > >
> > > Seems it is being passed as a literal.
> > >
> > > I am giving these as "-D" parameters to ant trying to pass them on to
> > > another program.
> > >
> > > Thanks for your help.
> > >
> > > <exec dir="." executable="some.exe">
> > > <arg path="${some.path}"/>
> > > <arg value="${some.value}"/>
> > > </exec>
> >
> > --
> > Larry V. Streepy, Jr.
> > Chief Technical Officer and VP of Engineering
> >
> > Health Language, Inc. -- "We speak the language of healthcare"
> >
> > 970/626-5028 (office) mailto:[EMAIL PROTECTED]
> > 970/626-4425 (fax) http://www.healthlanguage.com
--
Larry V. Streepy, Jr.
Chief Technical Officer and VP of Engineering
Health Language, Inc. -- "We speak the language of healthcare"
970/626-5028 (office) mailto:[EMAIL PROTECTED]
970/626-4425 (fax) http://www.healthlanguage.com
