Re: Updated : Failonerror does not have any effect on compilation failure

2007-08-31 Thread Vijay Aravamudhan
it would be better to call it using the task. That way the build will fail if any step or target fails. Exec creates a different process and so cannot cause the current build to fail. hth, Vijay Ravi Roy wrote: Hi All, I am calling ant.bat using in the following way :

Updated : Failonerror does not have any effect on compilation failure

2007-08-31 Thread Ravi Roy
Hi All, I am calling ant.bat using in the following way : I am using javac task inside projecbuild.xml and calling each project 's projectbuild.xml using task as shown above in the target. The

Failonerror does not have any effect on compilation failure

2007-08-31 Thread Ravi Roy
Hi All, I am calling ant.bat using in the following way : I am using javac task inside projecbuild.xml and calling each project 's projectbuild.xml using task as shown above in the target. The

Ant + JUnit

2007-08-31 Thread Joe Brutto
In my JUnit tests I have a series of public static methods embedded. When I run my tests, I receive: java.lang.Exception: No runnable methods Instead of requesting that the classes be ignored in the filter set for the batch run, is there any way to specify to ignore that "no runnable methods" er

Re: Getting around Set Property Values

2007-08-31 Thread Guru Balse
You can also consider passing in the destdir as an optional parameter (attribute) of the macro (with default value = [EMAIL PROTECTED]) David Weintraub wrote: Apparently, there are two methods: 1). Add the parameter name to my property name. Like this: 2). Use the Ant Contrib variables:

Re: Getting around Set Property Values

2007-08-31 Thread David Weintraub
Apparently, there are two methods: 1). Add the parameter name to my property name. Like this: 2). Use the Ant Contrib variables: 2a). Use the Ant Contrib var package, but to only reset the property: Although it would get me out of using the AntContrib library, I decided against prep

Re: Getting around Set Property Values

2007-08-31 Thread Peter Reilly
Currently you need to: 1 ) use 2) use the invent new property based on macro instance trick: for ant 1.8.0, we are considering implementing a "local" property: Peter On 8/31/07, David Weintraub <[EMAIL PROTECTED]> wrote

RE: Getting around Set Property Values

2007-08-31 Thread Burgess, Benjamin
You could use the parameter being passed in as part of the name of your property. Something like: Ben Burgess -Original Message-

Getting around Set Property Values

2007-08-31 Thread David Weintraub
Okay, I've got a quick question. Once a property is set, it can never be overridden. (Actually, you can use the AntContrib task 'variable' to do this, but...) I am defining a Maco that looks like this: When I call the Macro the first time, the proper

AW: Defining a set of jars for classpath, jar and manifest

2007-08-31 Thread Jan.Materne
... ... Jan >-Ursprüngliche Nachricht- >Von: Juergen Weber [mailto:[EMAIL PROTECTED] >Gesendet: Freitag, 31. August 2007 18:20 >An: user@ant.apache.org >Betreff: Defining a set of jars for classpath, jar and manifest > >Hi, > >for building an e

Defining a set of jars for classpath, jar and manifest

2007-08-31 Thread Juergen Weber
Hi, for building an ear archive I need a set of jars three times: 1) for the compiler classpath 2) for inclusion in the jar 3) an EJB's manifest classpath OK, on the web there are solutions for automatically creating Manifest classpathes, but how can you define only once the set of jars and use

Re: global variables

2007-08-31 Thread Peter Reilly
On 8/31/07, Rebhan, Gilbert <[EMAIL PROTECTED]> wrote: > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 30, 2007 4:10 PM > To: user@ant.apache.org > Subject: AW: global variables > > /* > Each property is global and immutable. > > ... > > u

RE: global variables

2007-08-31 Thread Rebhan, Gilbert
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, August 30, 2007 4:10 PM To: user@ant.apache.org Subject: AW: global variables /* Each property is global and immutable. ... unless you have a custom built Ant from HEAD (since Peters support for local

Re: SCP Task & umask

2007-08-31 Thread Eric Jain
Atsuhiko Yamanaka wrote: I have not tried it by myself yet, but it seems scp1 protocol allows us to choose the umask in sending files and creating directories. In the class, org.apache.tools.ant.taskdefs.optional.ssh.ScpToMessage the method 'sendFileToRemote' has explicitly chosen '0644'. As