Re: using ant on MacOS X beta

after reading the mailing list archives, I think my problem is the class loader. here's the stack trace from the crash: BUILD FAILED No JAXP compliant XML parser found. See http://java.sun.com/xml for the reference implementation. java.lang.NoClassDefFoundError:

Re: using ant on MacOS X beta

Paul, There's no inherent problem with running Ant on MacOS X PB - we've been using it solidly for the last six months or more (e.g. pre - PB as well!). Which version are you running - is it a recent CVS version or a full release like 1.2? Stuart. On Thursday, January 18, 2001, at 08:22 AM,

Re: using ant on MacOS X beta

problem appears to be fixed. it was indeed a corrupted file, I assume due to my decompressor. If anyone else has a similar problem with MacOS X public beta and ant, please tell them to go get a product called OpenUp from www.versiontracker.com . The utility that ships with the os has some

Re: Fully Automated Builds

-logfile mybuid.log should do it Filip ~ Namaste - I bow to the divine in you. ~ Filip Hanik Technical Architect [EMAIL PROTECTED] - Original Message - From: "Bevan Arps" [EMAIL PROTECTED] To: "Ant User Mailing List" [EMAIL PROTECTED] Sent: Thursday, January 18, 2001 3:26 PM Subject:

Re: Fully Automated Builds

Filip Hanik wrote: -logfile mybuid.log should do it This only captures ALL the ant output to a file (and includes all of the ANT overhead as well) - I want to capture the output of *each* compilation to a separate file. Eg: Say I trigger a build of a serious of CORBA services we are writing.

Re: Fully Automated Builds

create three different build.xml files and invoke them after each other inside your main build.xml you would have three different ant tasks, for each task you would specify the output. Take a look at the builtin task ANT since you are using the ANT task you only need to set global properties etc

RE: Fully Automated Builds

Filip Regarding logging the output of the builds: I am also doing the same kind of thing using ant on win-2000 platform. You might already be doing this, but to answer your question, there isn't any redirection type of attribute for outputs with javac, yet it can be done by simply implementing

RE: Instability in Ant

One possibly interesting thing. This problem only occurs for me when I run the Weblogic EJBC. I'm using Weblogic 5.1, service pack 8. Here is the sample output from Ant when my "master" build script fails: header: [echo] *** [echo] *

Re: Fully Automated Builds

Oh right -- I forgot ant lets you specify an output file. This is a reasonable way to do it -- except you don't need to break your build up into 3 different build.xml files -- just go ahead and ant to targets in the one you have now. Diane --- Filip Hanik [EMAIL PROTECTED] wrote: create three

RE: Fully Automated Builds

-Original Message- From: Diane Holt [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 18, 2001 7:22 PM To: [EMAIL PROTECTED] Subject: RE: Fully Automated Builds /snip As for logging the output of the javac tasks themselves, I'm guessing you could add an attribute (say, "logfile") to

Doc issues was: Re: Override of property

Hi Diane, I've just re-read the docs for ant and antcall and they seem quite clear now. Thank you for your detailed answers. There is one thing which I noticed: The failonerror attribute for the javac task is not listed in the list of attributes in the docs. Diane Holt wrote: --- Ioan

Re: Doc issues was: Re: Override of property

--- Ioan Mitrea [EMAIL PROTECTED] wrote: There is one thing which I noticed: The failonerror attribute for the javac task is not listed in the list of attributes in the docs. You need to look at the most recent index.html. Diane = ([EMAIL PROTECTED])