From user-return-64508-apmail-ant-user-archive=ant.apache.org@ant.apache.org Wed Apr 09 15:02:30 2008 Return-Path: Delivered-To: apmail-ant-user-archive@www.apache.org Received: (qmail 39104 invoked from network); 9 Apr 2008 15:02:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Apr 2008 15:02:30 -0000 Received: (qmail 69657 invoked by uid 500); 9 Apr 2008 15:02:26 -0000 Delivered-To: apmail-ant-user-archive@ant.apache.org Received: (qmail 69628 invoked by uid 500); 9 Apr 2008 15:02:26 -0000 Mailing-List: contact user-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Ant Users List" Reply-To: "Ant Users List" Delivered-To: mailing list user@ant.apache.org Received: (qmail 69617 invoked by uid 99); 9 Apr 2008 15:02:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Apr 2008 08:02:26 -0700 X-ASF-Spam-Status: No, hits=-4.0 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of Shawn.Castrianni@halliburton.com designates 34.254.16.16 as permitted sender) Received: from [34.254.16.16] (HELO HOUMAIL004.halliburton.com) (34.254.16.16) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Apr 2008 15:01:42 +0000 Received: from HOUEXHU010.corp.halliburton.com (houexhu010.corp.halliburton.com [34.224.232.94]) by HOUMAIL004.halliburton.com (8.13.8/8.13.8) with ESMTP id m39F1JBt012178 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Wed, 9 Apr 2008 10:01:47 -0500 Received: from HOUEXCH012.corp.halliburton.com ([34.224.232.93]) by HOUEXHU010.corp.halliburton.com ([34.224.232.94]) with mapi; Wed, 9 Apr 2008 10:00:06 -0500 From: Shawn Castrianni To: "'Ant Users List'" Date: Wed, 9 Apr 2008 10:00:06 -0500 Subject: RE: exec task Thread-Topic: exec task Thread-Index: AciZ8kLw7gLCEaV/TL2oI1YEX0Tk1QAXhjPwAAB8FIA= Message-ID: <745B9EDF57802349B13F90E4E0B4B86C3B9F1D5B5C@HOUEXCH012.corp.halliburton.com> References: <745B9EDF57802349B13F90E4E0B4B86C3B9F1D5B52@HOUEXCH012.corp.halliburton.com> <65908F7202981E4C9D6FDE92D60BBE6E0D87F544@whexchmb03.bsna.bsroot.bear.com> In-Reply-To: <65908F7202981E4C9D6FDE92D60BBE6E0D87F544@whexchmb03.bsna.bsroot.bear.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=4.65.7111:2.4.4,1.2.40,4.0.164 definitions=2008-04-09_05:2008-04-09,2008-04-09,2008-04-09 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=3.1.0-0803050000 definitions=main-0804090079 X-Virus-Checked: Checked by ClamAV on apache.org Will the semicolon trick of executing more than one command with one exec t= ask work on all platforms?? --- Shawn Castrianni -----Original Message----- From: Vallon, Justin [mailto:jvallon@bear.com] Sent: Wednesday, April 09, 2008 9:54 AM To: Ant Users List Subject: RE: exec task Shawn, 'exec' runs a process. Side-effects (environment variables, etc) that happen in the process are lost when the process exits. If you want this behavior, then you could generate a script on the fly that does the equivalent ("set-some-vars\nrun-the-command\n"). If you want one task to choose the vars, and another to run the command, then you could create a temporary file that contains config info that is built up as the tasks execute: init-config: create empty "config" file setup (depends on init-config): append "set-some-vars" to config setup2 (depends on init-config): append "set-other-vars" to config run (depends on setup and setup2): exec "config ; run-command" -Justin office 8-383-6725, 212-272-6725; cell 917-861-6042 -----Original Message----- From: Shawn Castrianni [mailto:Shawn.Castrianni@halliburton.com] Sent: Tuesday, April 08, 2008 11:32 PM To: 'user@ant.apache.org' Subject: exec task Oh yeah, and it would be nice if one exec task could continue a previous exec task environment. So if one exec task calls a batch file that sets some env variables or something, the next exec task could have an option to continue the environment setup by the previous exec task and execute something else with the batch file already having been run. --- Shawn Castrianni ---------------------------------------------------------------------- This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient. Any review, use, distribution, or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message. *********************************************************************** Bear Stearns is not responsible for any recommendation, solicitation, offer or agreement or any information about any transaction, customer account or account activity contained in this communication. *********************************************************************** --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@ant.apache.org For additional commands, e-mail: user-help@ant.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@ant.apache.org For additional commands, e-mail: user-help@ant.apache.org