You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by bu...@apache.org on 2002/05/13 05:31:22 UTC
DO NOT REPLY [Bug 9017] New: -
No whitespaces allowed for porperties on command line
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9017>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9017
No whitespaces allowed for porperties on command line
Summary: No whitespaces allowed for porperties on command line
Product: Ant
Version: 1.4
Platform: All
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: Core
AssignedTo: ant-dev@jakarta.apache.org
ReportedBy: hardy@youramigo.com
It is not possible to parse a property containing a whitespace into the build
process using the -D option, eg:
ant -Doptions="this are the options I need in the build" all.
In some cases this might be useful, eg I have a target which executes another
programm via exec and I would like to do something like this:
<exec executable="my executable">
<arg line="${options}"/>
</exec>
I checked the implementation for the command line parsing in
org.apache.tools.ant.Main. It seems to me that the algorithm used to parse
the options is quite rudimentary. It relies on the args[] array which is passed
into main. What's about using the gnu.getopt package or beeing just a bit
smarter with the -D options
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>