Re: How to get varaibles recognized by this task

2009-03-05 Thread Antoine Levy Lambert
Hello Dave, you should pass the projectName as an argument, so if you put it after the other arguments, I guess inside your script you would have sys.argv[4] instead of ${projectName} Regards, Antoine dave.alvar...@remanresource.com wrote: Hi, I have the below target ...

Re: How to get varaibles recognized by this task

2009-03-05 Thread Scot P. Floess
Mar 2009, dave.alvar...@remanresource.com wrote: Thanks for your reply. I'm unfamiliar with some of the terms you are mentioning below. Could you give a code example? - Dave ---Original Message--- From: Scot P. Floess Subject: Re: How to get varaibles recognized by this ta

Re: How to get varaibles recognized by this task

2009-03-05 Thread dave.alvarado
Thanks for your reply. I'm unfamiliar with some of the terms you are mentioning below. Could you give a code example? - Dave > ---Original Message--- > From: Scot P. Floess > Subject: Re: How to get varaibles recognized by this task > Sent: Mar 05 '09 1

Re: How to get varaibles recognized by this task

2009-03-05 Thread Scot P. Floess
I know, at least using scriptdef, I was able to make calls out to attributes.get ( [attribute-name] ) using beanshell - of course assuming my scriptdef contained an element On Thu, 5 Mar 2009, dave.alvar...@remanresource.com wrote: Hi, I have the below target ...

How to get varaibles recognized by this task

2009-03-05 Thread dave.alvarado
Hi, I have the below target ... print 'Calling the script ...' connect(sys.argv[1],sys.argv[2],sys.argv[3]) shutdownCluster("my_cluster_1") undeploy("RoutingEngine#v1.0") removeApplication("RoutingEngine#v1.0") deploy('RoutingEngine#v1.0'