But the user must still specify the command line as a single line and so there is still a basic problem with embedded spaces. If we could have tags for each parameter then embedded spaced would not be a problem. True, this would break a lot of code and so a different task is needed. Then one could begin a migration of existing tasks that are using the single command line.
Cory Wandling Object Dynamics, Inc. He is no fool who gives up that which he cannot keep - Jim Elliot ----- Original Message ----- From: Stefan Bodewig <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, August 10, 2000 10:09 AM Subject: Re: problem with commandlines > >>>>> "CW" == Cory Wandling <[EMAIL PROTECTED]> writes: > > CW> When I have built things like this I have always used the > CW> String[] version of exec. > > This is what the current (CVS) exec task does. > > The problem comes in when we need to change the working directory of > the spawned process. JDK 1.3 has a method to do this (and we use it, > thanks Jesse), the Mac seems to handle this if we set user.dir. On > Win9x and Unix we use a shell script, this one gets the parameters via > the String[] call but doesn't quote the correctly when invoking the > desired command. > > Stefan
