Return-Path: 
 <dev-return-67605-apmail-ant-dev-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-dev-archive@www.apache.org
Received: (qmail 84575 invoked from network); 9 Jun 2005 11:31:03 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 9 Jun 2005 11:31:03 -0000
Received: (qmail 2338 invoked by uid 500); 9 Jun 2005 11:31:01 -0000
Delivered-To: apmail-ant-dev-archive@ant.apache.org
Received: (qmail 2263 invoked by uid 500); 9 Jun 2005 11:31:01 -0000
Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:dev-unsubscribe@ant.apache.org>
List-Help: <mailto:dev-help@ant.apache.org>
List-Post: <mailto:dev@ant.apache.org>
List-Id: "Ant Developers List" <dev.ant.apache.org>
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Delivered-To: mailing list dev@ant.apache.org
Received: (qmail 2233 invoked by uid 99); 9 Jun 2005 11:31:00 -0000
X-ASF-Spam-Status: No, hits=0.6 required=10.0
	tests=NO_REAL_NAME,PLING_PLING
X-Spam-Check-By: apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Received: from dnsinet.rzf-nrw.de (HELO dnsinet.rzf-nrw.de) (193.109.238.66)
  by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 09 Jun 2005 04:30:59 -0700
Received: from z011100.bk.fin.local (z011104.bk.fin.local [193.109.238.140])
	by dnsinet.rzf-nrw.de (8.12.10/8.12.10) with ESMTP id j59BUPri011943
	for <dev@ant.apache.org>; Thu, 9 Jun 2005 13:30:25 +0200
Received: from z011134.bk.fin.local ([130.11.7.134]) by z011100.bk.fin.local
 with Microsoft SMTPSVC(6.0.3790.0);
	 Thu, 9 Jun 2005 13:30:27 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: AW: Can you help me!!!
Date: Thu, 9 Jun 2005 13:30:08 +0200
Message-ID: <3CD9A35A043C094EA8773DBB698E801B01865C83@z011134.bk.fin.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Can you help me!!!
Thread-Index: AcVs5cLxJv9FGzHlRjKhGkH9wT//ZQAAMZyw
From: <Jan.Materne@rzf.fin-nrw.de>
To: <dev@ant.apache.org>
X-OriginalArrivalTime: 09 Jun 2005 11:30:27.0189 (UTC)
 FILETIME=[A2582250:01C56CE6]
X-Virus-Checked: Checked
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

Once asked is enough - you=B4ll writing to a complete mailinglist ...

Jan=20

>-----Urspr=FCngliche Nachricht-----
>Von: Srinivas [mailto:csrini@mahindrabt.com]=20
>Gesendet: Donnerstag, 9. Juni 2005 12:23
>An: Ant Developers List
>Betreff: Can you help me!!!
>
>
>Dear Smith,
>
> 	I am new to ant Scripting.  My requirement is like=20
>this.  We are using Weblogic.
>
>         I receive an .EAR file and before deployment my BUILD=20
>should do the following.
>=09
>
>		a. My Script should locate the=20
>weblogic-ejb-jar.xml inside the .EAR and=20
><trans-time-out></trans-time-out>
>		   Element should be modified per EJB basis.
>
>	What do you suggest?
>=09
>
>Regards,
>Srini.
>
>-----Original Message-----
>From: Phil Weighill-Smith [mailto:phil.weighill-smith@volantis.com]
>Sent: Sunday, May 29, 2005 8:42 PM
>To: Ant Developers List
>Subject: RE: A possible solution for conditional execution of tasks?
>
>
>There is the option to use the conditional task ("if") from=20
>ant-contrib... this allows the nesting of a "sequential" task=20
>which itself can contain any tasks you want.
>
>	-----Original Message-----
>
>	From: Sandip Chitale [mailto:Sandip.Chitale@Sun.COM]
>
>	Sent: Sun 29/05/2005 16:06
>
>	To: Ant Developers List
>
>	Cc:
>
>	Subject: Re: A possible solution for conditional=20
>execution of tasks?
>
>
>
>
>
>	Phil Weighill-Smith wrote:
>
>
>	>My opinion regarding the disadvantages of this approach:
>	>
>	>*      Antcall has to create a whole new Project in=20
>memory in order to work and is therefore an inefficient task
>	>
>
>	>
>	Yes. If the project is large this could be a large=20
>overhead. It seems
>	the semantics of antcall is not like a sub target but=20
>more like a target
>	in a sub project (even though the project happens to be the same
>	project).  Is there a more lightweight solution planned=20
>in this area?
>
>
>	>*      If something invoked via Antcall depends on a=20
>target that is also depended on by something depending on the=20
>target invoking Antcall then this dependency target will be=20
>executed more than once because dependencies are not handled=20
>across Antcall invocations
>	>
>
>	>
>	Yes.
>
>
>	>*      The dependency tree is "interrupted" and=20
>graphing tools that can show ant build script structures will=20
>not (generally) work correctly and show the whole dependency tree
>	>
>
>	>
>	I did not think about the graphing tools, but that is a=20
>good point also.
>
>
>	Given the fact that you did not list any advantages it=20
>seems this is not
>	a good idea.
>
>
>	>It might be better to add "if" and "unless" to the=20
>standard ant Task to allow for conditional execution, or even=20
>add a nested "condition" to the standard ant Task to allow for=20
>conditional execution. To provide BC with the standard=20
>"execute" method, the condition/if/unless processing would=20
>need to happen outside this method.
>	>
>
>	>
>	This seems like this is the real answer. However I read=20
>somewhere that
>	it is an architectural decision to not support "if" and=20
>"unless" etc. at
>	the task level. Can anyone point me to a=20
>discussion/document on that?
>
>
>	What about using scripting? Is that not recommended either?
>
>
>	Google search revealed that many people are looking for=20
>solutions for
>	similar problems.
>
>
>	Regards,
>	Sandip
>
>
>	>
>	>Phil :n.
>	>
>	>       -----Original Message-----
>	>       From: Sandip Chitale [mailto:Sandip.Chitale@Sun.COM]
>	>       Sent: Sat 28/05/2005 18:56
>	>       To: dev@ant.apache.org
>	>       Cc:
>	>       Subject: A possible solution for conditional=20
>execution of tasks?
>	>    =20
>
>	>    =20
>
>	>
>	>       To conditionally execute a step in Ant one has=20
>to resort to setting up a
>	>       target structure like this:
>	>    =20
>
>	>       :
>	>       <target name=3D"predicate">
>	>          <condition property=3D"condition-satisfied">
>	>              <available .../>
>	>          :
>	>          </condition>
>	>       </target>
>	>    =20
>
>	>       <target name=3D"conditional-step"=20
>if=3D"condition-satisfied">
>	>          <!-- conditional tasks here -->
>	>          :
>	>          :
>	>       </target>
>	>    =20
>
>	>       <target name=3D"conditional" depends=3D"predicate,=20
>conditional-step"/>
>	>    =20
>
>	>       <target name=3D"main" depends=3D"conditional">
>	>          :
>	>          :
>	>       </target>
>	>       :
>	>    =20
>
>	>       This is because of several reasons:
>	>    =20
>
>	>           * The ant tasks do not have something like=20
>*if* attribute.
>	>           * One cannot get away with only two targets=20
>instead of three because
>	>             the dependencies are executed before the=20
>dependent. Using the
>	>             above example it is not possible to do=20
>what target predicate does
>	>             in the main target and avoid using the=20
>predicate target.
>	>           * Ensure order of execution
>	>    =20
>
>	>       However, I tried a solution making use of=20
>antcall task and it worked. It
>	>       works as follows:
>	>    =20
>
>	>       :
>	>       <target name=3D"conditional-step"=20
>if=3D"condition-satisfied">
>	>          <!-- conditional tasks here -->
>	>          :
>	>          :
>	>       </target>
>	>    =20
>
>	>       <target name=3D"main" depends=3D"conditional-step">
>	>       :
>	>          <condition property=3D"condition-satisfied">
>	>              <available .../>
>	>          :
>	>          </condition>
>	>          <antcall target=3D"condition-satisfied"/>
>	>          :
>	>       </target>
>	>    =20
>
>	>       The advantage of this approach is to quickly=20
>have some tasks execute
>	>       conditionally by putting them in a target and=20
>calling that target using
>	>       antcall after setting some property.
>	>    =20
>
>	>       And it seemed to work. My question is - is=20
>there a problem using this
>	>       approach? Why or why isn't this a preferred approach?
>	>    =20
>
>	>       Thanks in advance,
>	>       Sandip
>	>    =20
>
>	>    =20
>
>	>
>	>
>
>	>
>
>
>
>
>=09
>---------------------------------------------------------------------
>	To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>	For additional commands, e-mail: dev-help@ant.apache.org
>
>
>
>
>
>
>
>*********************************************************
>Disclaimer:
>
>The contents of this E-mail (including the contents of the=20
>enclosure(s) or attachment(s) if any) are privileged and=20
>confidential material of MBT and should not be disclosed to,=20
>used by or copied in any manner by anyone other than the=20
>intended addressee(s).   In case you are not the desired=20
>addressee, you should delete this message and/or re-direct it=20
>to the sender.  The views expressed in this E-mail message=20
>(including the enclosure(s) or attachment(s) if any) are those=20
>of the individual sender, except where the sender expressly,=20
>and with authority, states them to be the views of MBT.
>
>This e-mail message including attachment/(s), if any, is=20
>believed to be free of any virus.  However, it is the=20
>responsibility of the recipient to ensure that it is virus=20
>free and MBT is not responsible for any loss or damage arising=20
>in any way from its use
>
>*********************************************************
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>For additional commands, e-mail: dev-help@ant.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org