RE: set jvm to 1.3

Hi, Tahnks for reply. So there is not way to turn off this 'polite information'? Since we have a assert keyword in our java 1.3 code and this generates plenty of annoying warnings. //Mikael -Original Message- From: James Abley [mailto:[EMAIL PROTECTED] Sent: den 18 mars 2005 08:44

RE: set jvm to 1.3

On Fri, 2005-03-18 at 07:20, Mikael Petterson (KI/EAB) wrote: > Hi, > > I have set javac's source attribute to 1.3 but when I compile the code I > get, > > ".. warning: as of release 1.4, assert is a keyword..." > > I start ant with 1.4.2 so I guess that is the default for compiling code to.

AW: Exiting ant TARGET without aborting build

... ... error message Jan > -Ursprüngliche Nachricht- > Von: Michael Pelz Sherman [mailto:[EMAIL PROTECTED] > Gesendet am: Donnerstag, 17. März 2005 20:56 > An: Ant Users List > Betreff: Re: Exiting ant TARGET without aborting build > > Yeah, yeah, I know. :-) >

RE: set jvm to 1.3

Hi, I have set javac's source attribute to 1.3 but when I compile the code I get, ".. warning: as of release 1.4, assert is a keyword..." I start ant with 1.4.2 so I guess that is the default for compiling code to. As I understand it the javac command with option '-source 1.3' would make the

RE: Ant's mail task

Hi Antoine, I tried the SetProxy task but it didn't help. The task still fails and gives me the following error [mail] Failed to initialise MIME mail: javax/mail/MessagingException [mail] Sending email: "" Does that mean anything?? Archit -Original Message- From: Antoine Levy-Lambert [

Re: Ant's mail task

Hello, there is a SetProxy task in the ant optional tasks. Unfortunately, a glimpse in the code suggests that it might not work for mail. the task is able to define http, ftp and socks proxy hosts and ports, but does not mention anything about SMTP. Cheers, Antoine [EMAIL PROTECTED] wrote: Hi,

Ant's mail task

Hi, I am using ant's mail task behind a proxy server but the task fails. I tried userid and password but that doesn't help. Can anyone help me? Archit CEG, Tech Cell, PUNE Mastek Ltd. "Only two things are infinite, the Universe and human stupidity and I'm not sure about the former" MASTE

How to make imported targets always able to use "project.target"?

I want to be able to use the imports always as "project.target", as in: import "${basedir}/common.xml" Is this possible? It looks like (from viewing debug output of my scripts) that unless the imported target is already defined in the importing script, the project base isn't usable. This

Re: parse file in ant and create new file

Looks like a filtered to me. -Matt --- Radha Sangal <[EMAIL PROTECTED]> wrote: > Is there any task in ant to simulate this simple > code of java , reading > one file and extracting content to write into > another... in integrate > this small java code , I will have to do lot of > work.. was wond

parse file in ant and create new file

Is there any task in ant to simulate this simple code of java , reading one file and extracting content to write into another... in integrate this small java code , I will have to do lot of work.. was wondering if its possible through ant itself BufferedReader in = new BufferedReader(new FileR

Re: Exiting ant TARGET without aborting build

Yeah, yeah, I know. :-) Mostly, I was just curious if such a thing were possible. But I think there is a good argument to be made for this kind of task. After all, if one has to break up a functionally "atomic" target into a whole bunch of sub-targets which will never be re-used, that's a lot more

Re: Transparent access to files/resources

--- Yves Martin <[EMAIL PROTECTED]> wrote: [SNIP] > Is there a way to use resources easily in Ant ? IMHO not at the moment. We are looking into something along these lines for Ant 1.7 . -Matt > Thank you in advance > > Regards, > -- > Yves Martin > > > ---

Re: Exiting ant TARGET without aborting build

On Mar 17, 2005, at 10:04 AM, Michael Pelz Sherman wrote: I'd like to be able to do something like this: (condition check here) (do more-tasks...) There's a general pattern that may be in play here... whenever you have a target that's starting to look li

Re: Exiting ant TARGET without aborting build

Not ideal but you can use the task with antcontrib's . -Matt --- Michael Pelz Sherman <[EMAIL PROTECTED]> wrote: > Yes, I meant from inside the buildfile. Sorry - > actually I mean to say > "target", not "task". I'd like to be able to do > something like this: > > > > > > >

Re: Exiting ant TARGET without aborting build

Yes, I meant from inside the buildfile. Sorry - actually I mean to say "target", not "task". I'd like to be able to do something like this: (condition check here) (do more-tasks...) The "exit" task would simply exit the target, but would not abort th

RE: set jvm to 1.3

AFAIK, target means to what version of class format must the compiled classes conform to; compiler means what compiler exactly should be used for compilation (i.e. to produce these classes). HTH Ivan --- "Mikael Petterson (KI/EAB)" <[EMAIL PROTECTED]> wrote: > Hi again, > > So what is the differ

RE: set jvm to 1.3

On Thu, 2005-03-17 at 14:00, Mikael Petterson (KI/EAB) wrote: > Hi again, > > So what is the difference of > > javac attributes "target" and "compiler". > If I want to make sure that my code is compilable for 1.3? > I am getting somewhat confused. > > //Mikael compare with `javac -help` for the

RE: set jvm to 1.3

Hi again, So what is the difference of javac attributes "target" and "compiler". If I want to make sure that my code is compilable for 1.3? I am getting somewhat confused. //Mikael -Original Message- From: Ivan Ivanov [mailto:[EMAIL PROTECTED] Sent: den 17 mars 2005 14:53 To: Ant Users L

RE: set jvm to 1.3

--- "Mikael Petterson (KI/EAB)" <[EMAIL PROTECTED]> wrote: > Thanks for the hint! > > In ant there is a property called: > > ant.java.version It is the java version ant is started with. > > What does that tell us? Does it say anything about > the version of compiler used? I suppose it does not

RE: set jvm to 1.3

Thanks for the hint! In ant there is a property called: ant.java.version What does that tell us? Does it say anything about the version of compiler used? Or is it the jvm that ant was started with? //Mikael -Original Message- From: Ivan Ivanov [mailto:[EMAIL PROTECTED] Sent: den 17 mar

Re: set jvm to 1.3

See target attribute of task. You can do it like this: , define javac.target properties in your build.properties as javac.target=1.3 HTH Ivan --- "Mikael Petterson (KI/EAB)" <[EMAIL PROTECTED]> wrote: > Hi, > > I am starting ant 1.6.1 with jdk1.4.2 but I need to > compile my code with 1.3. >

set jvm to 1.3

Hi, I am starting ant 1.6.1 with jdk1.4.2 but I need to compile my code with 1.3. How can I set this in my build.properties and then use in my javac task? Any hints? //Mikael - To unsubscribe, e-mail: [EMAIL PROTECTED] For addi

Re: putting it together

On Thu, 17 Mar 2005 11:43:57 +0100, Stefan Bodewig <[EMAIL PROTECTED]> wrote: > On Thu, 17 Mar 2005, THUFIR HAWAT <[EMAIL PROTECTED]> wrote: > > > file and mode attributes are types of tags? > > The Ant manual assumes you are at least vaguely familiar with XML > terms. > > is the element foo.

Transparent access to files/resources

Hello, I would like to be able to use Ant tasks either with a file stored on the disk or with a file stored in a jar file (as a resource). I think it is not possible (I may be wrong) and it means a large refactoring concerning file access in Ant. But for me that feature will be a great he

Re: does ant support jdk1.5

Hi, That was wonderful info. My code didnt work just because there are some errors in the project which were not detected by eclipse(enums in java1.5.0) but were shown as errors by the java compiler v1.5 in the console. Sorry for the inconvenience I thought it was compatibility issue bw ant and

Re: putting it together

On Thu, 17 Mar 2005, THUFIR HAWAT <[EMAIL PROTECTED]> wrote: > file and mode attributes are types of tags? The Ant manual assumes you are at least vaguely familiar with XML terms. is the element foo. is an element foo with an attribute bar, that attribute has the value baz. is an element fo

putting it together

List: ant-user Subject:Re: putting it together From: Stefan Bodewig Date: 2005-03-17 8:40:32 Message-ID: [Download message RAW] On Thu, 17 Mar 2005, THUFIR HAWAT <[EMAIL PROTECTED]> wrote: > but, how do you put these together into a target? By reading the first paragraph

Re: "Infinite Logging" when logging with log4j listener

On Thu, 17 Mar 2005, Klaus Allwicher <[EMAIL PROTECTED]> wrote: > Any ideas why this error occurs and how I can resolve it ? It is log4j itself that is writing to System.out. This will be fixed in Ant 1.6.3 (and is fixed in nightly builds) expected to be released in a few weeks.

"Infinite Logging" when logging with log4j listener

Hi, I have problems configuring ANT to use the log4j listener. Everything works fine until, I invoke a self written java class with the task. This java class also uses log4j for logging purposes. After the successful execution of the java class, the next task fails with the message: xxx:

Re: putting it together

On Thu, 17 Mar 2005, THUFIR HAWAT <[EMAIL PROTECTED]> wrote: > but, how do you put these together into a target? By reading the first paragraph under the headline "manifest" in which says , | This element is identical to the manifest task, bu

putting it together

sample: from sample: from but, how do you put these tog