in reply to Ant, Perl, and where did my STDOUT go?

This looks like a Java question to me. There's no Perl in here, so it's a bit hard to say (perhaps the Perl program closes STDOUT, who knows?). But it's easy to check whether it's a Java question or not. Replace the Perl command with something else that writes to STDOUT. If that output also disappears, you'd have to dive in your Java manuals.

Abigail

  • Comment on Re: Ant, Perl, and where did my STDOUT go?

Replies are listed 'Best First'.
Re: Re: Ant, Perl, and where did my STDOUT go?
by P0w3rK!d (Pilgrim) on Jun 04, 2002 at 15:19 UTC
    I executed the following by itself:
    commandLine.setExecutable(getPerlCommand()); commandLine.createArgument().setValue("-h");
    and it worked fine:
    C:\ant\bin>ant
    Buildfile: build.xml
    
    main:
    foo c:\perl\bin\perl.exe -h
    
    foo Usage: c:\Perl\bin\perl.exe switches -- programfile arguments
    foo   -0octal       specify record separator (\0, if no argument)
    foo   -a              autosplit mode with -n or -p (splits $_ into @F)
    foo   -c              check syntax only (runs BEGIN and END blocks)
    foo   -d:debugger   run scripts under debugger
    foo   -Dnumber/list set debugging flags (argument is a bit mask or flags)
    foo   -e 'command'    one line of script. Several -e's allowed. Omit programfile.
    foo   -F/pattern/     split() pattern for autosplit (-a). The //'s are optional.
    foo   -iextension   edit <> files in place (make backup if extension supplied)
    foo   -Idirectory     specify @INC/#include directory (may be used more than once)
    foo   -loctal       enable line ending processing, specifies line terminator
    foo   -mM-module.. executes `use/no module...' before executing your script.
    foo   -n              assume 'while (<>) { ... }' loop around your script
    foo   -p              assume loop like -n but print line also like sed
    foo   -P              run script through C preprocessor before compilation
    foo   -s              enable some switch parsing for switches after script name
    foo   -S              look for the script using PATH environment variable
    foo   -T              turn on tainting checks
    foo   -u              dump core after parsing script
    foo   -U              allow unsafe operations
    foo   -v              print version number, patchlevel plus VERY IMPORTANT perl info
    foo   -V:variable   print perl configuration information
    foo   -w              TURN WARNINGS ON FOR COMPILATION OF YOUR SCRIPT. Recommended.
    foo   -xdirectory   strip off text before #!perl line and perhaps cd to directory
    foo
    

    The question now would be, how do I encapsulate the script and *its* command line variables and call it with Perl? Otherwise, it appears Perl may not be executing the script at all...

    Thank you :>

    -P0w3rK!d