Re: different patterns per configuration

2011-06-30 Thread Shaka Tard
Oh, that's actually not too bad. I hope other more experienced folks would be willing to correct me if I am wrong, but this seems fairly straightforward. You would use ivy:retrieve twice in your ANT script to get the libraries from your local cache, and the pattern you use inside there will dicta

Re: Syntax for Names: target, property, macrodef, etc.

2011-06-30 Thread Matt Benson
On Thu, Jun 30, 2011 at 11:50 AM, Steve Amerige wrote: > Hi Dominique and all, > > After considering that scriptdef, macrodef, and perhaps some other tags do > not allow neither the "-" nor the "." as an initial character, I'm going to > use the "_" character name prefix to indicate that a name is

Re: Syntax for Names: target, property, macrodef, etc.

2011-06-30 Thread Steve Amerige
Hi Dominique and all, After considering that scriptdef, macrodef, and perhaps some other tags do not allow neither the "-" nor the "." as an initial character, I'm going to use the "_" character name prefix to indicate that a name is "local" to the current JVM. For example: Again, the point

Re: Syntax for Names: target, property, macrodef, etc.

2011-06-30 Thread Matt Benson
On Thu, Jun 30, 2011 at 10:54 AM, Dominique Devienne wrote: > On Thu, Jun 30, 2011 at 8:31 AM, Dominique Devienne > wrote: >> On Thu, Jun 30, 2011 at 6:51 AM, Steve Amerige wrote: >>> I'm looking for the authoritative specification within Ant for the value of >>> the name attribute >> PS: Also

Re: different patterns per configuration

2011-06-30 Thread teknokrat
Shaka Tard writes: > > Teknocrat, > > First, are you saying you need to see both jars, for instance, like this? > > commons-lang.jar > commons-lang-1.6.10.jar no, I want some jars going into conf1 as foo-1.2.jar and others going into conf2 as bar.so I am doing JNI and using ivy to store some

Re: Syntax for Names: target, property, macrodef, etc.

2011-06-30 Thread Dominique Devienne
On Thu, Jun 30, 2011 at 8:31 AM, Dominique Devienne wrote: > On Thu, Jun 30, 2011 at 6:51 AM, Steve Amerige wrote: >> I'm looking for the authoritative specification within Ant for the value of >> the name attribute > PS: Also keep in mind that property expansion does occurs inside these > names

passing paramter to eclipse arguments

2011-06-30 Thread kasim ahmed
I am trying to run test cases with some system aruguments given below. Arguments is not considering for build.xml through eclipse. Steps followed are given below. 1) by command prompt ant5 junit -DappRoot=ECM -DappName=ESW -Dapp.module=FNT -Dapp.env=LOC -DcloneNumber=1 2) by Eclipse: Eclipse->

Re: Syntax for Names: target, property, macrodef, etc.

2011-06-30 Thread Steve Amerige
Hi Dominique, Thanks for the info. And, also thanks for the specific example of the leading "-" character. Because Ant has only a global namespace for property names (and other names like macrodef, etc.), and for the case that a particular ant script inherits properties from the caller, I'm a

Re: Syntax for Names: target, property, macrodef, etc.

2011-06-30 Thread Dominique Devienne
On Thu, Jun 30, 2011 at 6:51 AM, Steve Amerige wrote: > I'm looking for the authoritative specification within Ant for the value of > the name attribute as in: > > > > > > and so forth.  I can't find within the Ant manual any BNF that defines what > a valid name is allowed to be. Anything goes

Syntax for Names: target, property, macrodef, etc.

2011-06-30 Thread Steve Amerige
I'm looking for the authoritative specification within Ant for the value of the name attribute as in: and so forth. I can't find within the Ant manual any BNF that defines what a valid name is allowed to be. I do see: http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#