RE: problem with macrodef in ant

2009-07-29 Thread edumudi.viswan...@oracle.com
Hi Scot P. Floess, I changed according to ur suggestion. It worked. Can u alloborate your exploration for the below two code blocks. condition property=binding.arg value='-b @{bindingfile}' not equals arg1=@{bindingfile} arg2=/ /not /condition property name=binding.arg

RE: problem with macrodef in ant

2009-07-29 Thread Scot P. Floess
The only real exploration I did was to review your code ;) When I saw the condition blocks and how you were using them in the java task it just seemed you were trying to use properties like variables - that is why I initially mentioned Ant Contrib's var task... I took a closer look and saw

Re: annotations are only available if source level is 5.0

2009-07-29 Thread Greg Roodt
Try this: javac srcdir=${src} classpathref=classpath destdir=${bin} target=1.5 source=1.5 / On Wed, Jul 29, 2009 at 1:00 PM, jann1 ja...@uni-landau.de wrote: Hello all, opensuse11.1, openbravoERP-250MP2: ant install.source produces the following error: compile: [javac] Compiling

Re: annotations are only available if source level is 5.0

2009-07-29 Thread jann1
Scot P. Floess schrieb: Which version of Java do you have on your system? If its stock 1.5+ it should just work without using the javac target attribute... java version 1.6.0_0 If all else fails I believe you can just do this: javac target=1.5 ... where to this javac target=1.5 ...

Re: annotations are only available if source level is 5.0

2009-07-29 Thread Greg Roodt
There should be a build.xml somewhere in the project. Probably /tmp/OpenbravoERP-2.50MP2/src-db/build in your case, but Im not familiar with this project/product. Inside the build.xml there will be an Ant target with a javac task. On Wed, Jul 29, 2009 at 1:15 PM, jann1 ja...@uni-landau.de

Re: annotations are only available if source level is 5.0

2009-07-29 Thread Scot P. Floess
Interesting... If you are running 1.6.0_0 - there should be absolutely no reason @Override is failing compilation... That is, unless your javac task has a target/source attribute of 1.4 or less... For example: javac target=1.4 source=1.4 ... You will need to search for build.xml or

Memory issue when using a lot of 'Ant' tasks.

2009-07-29 Thread Felix Dorner
Hey, Hey, I've written a task that repeatedly calls the 'Ant' task to execute another target. (The number of times that target is called Depends on the size of a given FileSet). The problem is that I get an OutOfMemory error. Wanted to ask if the following code looks suspicious to anyone. If

RE: Problem with zip task

2009-07-29 Thread Cole, Derek E
Yes, they are. -Original Message- From: Greg Roodt [mailto:gro...@gmail.com] Sent: Tuesday, July 28, 2009 5:51 PM To: Ant Users List Subject: Re: Problem with zip task Out of interest, are archive.dir and staging.dir on the same filesystem? On Tue, Jul 28, 2009 at 7:29 PM, Scot P.

RE: Problem with zip task

2009-07-29 Thread Cole, Derek E
I don't think this will be possible really. The filesystem is actually a clearcase snapshot view on that NAS...it gets a set of default permissions when the view is created/updated. -Original Message- From: Alexey N. Solofnenko [mailto:alexey.solofne...@symyx.com] Sent: Tuesday, July

compare files line by line

2009-07-29 Thread JĂșlio Cesar Bueno Cotta
Hello good people I am here again needing some help now I need to do a I script to compare two .properties..like First file Name: dev.properties @v...@=test1 @v...@=test2 @v...@=test3 Secund fiel Name: prd.properties # comment @v...@=test1 @v...@=test1037 @v...@=test4 I need to compare

Building with JDK 1.3. Which version of ANT?

2009-07-29 Thread Rez P
Hi I'm going back in time and have to compile and old java project with JDK 1.3. Currently I'm using Ant 1.7 and JDK 1.5 for all my projects. So when I wrote a build.xml for the jdk 1.3 code and in the compile target, using javac ant task, and set the 'source' or 'target' attributes to

Macosx and AnsiColorLogger

2009-07-29 Thread Ketan Padegaonkar
Hi, The AnsiColorLogger described at (http://ant.apache.org/manual/listeners.html#AnsiColorLogger) does not work on the apple terminal the same way it does on linux terminals. All the color output I get is gray and I've tried looking up google but nothing turned up. However other console apps

Re: Problem with zip task

2009-07-29 Thread Alexey N. Solofnenko
Oh, ClearCase. Each time we had similar problems we contacted our IT and they did some magic to fix it. I am happy to be [almost] Clear Case free now - there were so many things to go wrong and you cannot blame Rational/IBM for most of them, besides their architecture choices. If you need a

Re: Building with JDK 1.3. Which version of ANT?

2009-07-29 Thread Stefan Bodewig
On 2009-07-30, Rez P pon...@hotmail.com wrote: I'm going back in time and have to compile and old java project with JDK 1.3. Currently I'm using Ant 1.7 and JDK 1.5 for all my projects. So when I wrote a build.xml for the jdk 1.3 code and in the compile target, using javac ant task, and set

RE: Building with JDK 1.3. Which version of ANT?

2009-07-29 Thread Rez P
Thanks for the quick response Stefan. That's the part I couldn't understand! I did set my java_home to jdk 1.3! And added %java_home%\bin to my windows path variable. I believe where Ant error msg is coming from is my java consol control panel pointing to jre 1.3 as I had unchecked and

javac debug option not working

2009-07-29 Thread Kevin Javia
Hi, I am using Ant 1.7.1 with JDK 1.5.0_09. I am building three JAR files. Source JAR, Classes JAR with -g and Classes JAR without -g. javac debug=true debuglevel=lines,vars,source srcdir=${srcDir} destdir=${compiledWithgDir} classpath fileset dir=${classpathDir} include

Re: ivy promotion levels?

2009-07-29 Thread Mitch Gitman
Shawn, from what I've seen and heard, I would say that #1 above is a bare minimum but #2 above is also recommended. However, I would rephrase #2 from: set up separate resolvers so that each promotion level has its own top level directory such that promoting a module from one level to the next is

feature request: configuration intersections only implemented halfway

2009-07-29 Thread Garima Bathla
I've come to the conclusion that the new configuration intersections feature is implemented only halfway, and as a result it presents an inconsistent, misleading, confusing contract. Either we yank it out from Ivy entirely or we implement it fully. Suppose I have an Ivy module called system with

Re: feature request: configuration intersections only implemented halfway

2009-07-29 Thread Niklas Matthies
On Wed 2009-07-29 at 11:10h, Garima Bathla wrote on ivy-user: : Now, someone might argue, It's ambiguous how configuration intersections affect transitive dependencies. And I say to that, not so. It would be easy enough to do a logical proof that configuration intersections like