(Cc'ing ant-dev for thread continuity.. please don't reply there:)
Incidentally, 'diff -N' is not a general, nor cross-platform, solution
to the problem of how to convey updates.
I'd like to invent one though :) I was thinking along the lines of a
.jar file containing updates, with an Ant
sorry for the test
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Okay, I'm new, so bear with me.
I'm trying to setup the beginnings of a fairly large build script, that we
will use in a nightly/weekly build process. Eventually, automatic email
notifications, and all the trimming will be added, but First I need to
walk before I can run, so... I'm simply
Hi,
I'm trying to use the antlr optional task, but am having some
difficulty gettng ant to find antlr.jar. I was under the impression
that if I placed antlr.jar in ant's lib directory (along with
jakarta-ant-1.4.1-optional.jar) it would be found by the task, but
that's not happening. I get the
I might be suffering from too much turkey and seasonal brain-fog, but
when I started using ant, I began with little tiny scripts where the
effects (or not) were immediately obvious and if something looked funny,
or I didn't understand it, then I ran ant with the -v option to get
more details on
-Original Message-
From: John Volkar [mailto:[EMAIL PROTECTED]]
[...]
It's not a question of email notifiers.
The content of your email will be what you decide to send.
I recommend you to do 2 passes:
pass 1) build and log either via xml or plain text or both
pass 2) send the log
It depends on your e-mail notifier. If its a listener and throwing away
messageLogged events, then it wouldn't save echo's.
The code listed in the current Ant FAQ simply e-mails the build log file
(specified with -logfile log file name). The one that I added recently
(in the nightly builds,
-Original Message-
From: Paul Erion [mailto:[EMAIL PROTECTED]]
[...]
Anyone have any thoughts on what I might be doing wrong?
Unfortunately the Antlr task in = Ant 1.4.1 requires you to set Antlr in
the classpath.
It won't do anything if you drop the jar in ant/lib.
It should work
Erik,
Thanks for the help it is useful to start with a simple set of instructions.
I did do that and still see the same problem.
As far and the build success I still haven't put in the check for failure on
tests, but will do
as soon as I get this running.
-mez
- Original Message -
-Original Message-
From: Paul Erion [mailto:[EMAIL PROTECTED]]
Thanks for the quick response! At least I wasn't being totally brain
dead ... this time.
And another thanks for fixing this for 1.5 ... which I'll anxiously
be awaiting.
Ant 1.5 is not scheduled yet but should not
ok, i got it so it now accepts the parameters, but:
Cannot instantiate test case: testSubmitQueryMThread
junit.framework.AssertionFailedError: Cannot instantiate test case:
testSubmitQueryMThread
at junit.framework.Assert.fail(Assert.java:143)
at
- Original Message -
From: Jeff Turner [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: Ant Developers List [EMAIL PROTECTED]
Sent: Thursday, December 27, 2001 8:56 AM
Subject: [OT] Ant-driven update system (Re: Best way to add file to CVS
repository?)
Incidentally, 'diff -N' is not a
Please excuse my ignorance, but I am new to ant and junit.
My unit test reads a file and outputs a file. my problem is as long as my unit tests
do not read in or spit out a file
the test unit runs fine. what i get as an error when running with in ant and using
junit it can't find the file
even
Marcus,
The only way for us to help you is for you to post your test case code, and
your build.xml snippet that is calling the tests.
Are you referencing files by full path? Or by relative path? Are they in
the classpath?
Erik
- Original Message -
From: Marcus [EMAIL PROTECTED]
Erik,
build.xml snippet:
!-- RUN ALL THE TESTS IN THIS SECTTION maybe put this in an other
run_tests.xml file?? --
target name=run_tests depends=deploy_tests, deploy_debug
description=Execute Unit Tests
junit printsummary=yes fork=no haltonfailure=no
sysproperty
Hi,
You have a few options. Simplest is to put the condition on the
local-cleanup target itself:
target name=local-cleanup if=call_local_cleanup
...
/target
The contents of the local-cleanup target will only be executed if
call_local_cleanup is set (to any value, including values like
There are currently problems with the junit task when you set fork=no,
try setting fork to yes on you junit task, and see if that doesn't solve
the problem.
-Michael
On Thu, Dec 27, 2001 at 01:34:22PM -0800, Marcus wrote:
Erik,
build.xml snippet:
!-- RUN ALL THE TESTS IN THIS SECTTION
Micheal,
I did, and was just trying to see some symptoms for my own knowledge base,
or is that lack there of??
thanks
-mez
- Original Message -
From: Michael Brailsford [EMAIL PROTECTED]
To: Ant Users List [EMAIL PROTECTED]
Sent: Thursday, December 27, 2001 3:32 PM
Subject: Re:
I just upgraded to ant 1.4.1, and I can no longer build from within vim.
things worked just fine for ant 1.3, but for some reason 1.4.1 will not
work. When I use the command :!ant -find build.xml, the output I get
is
Searching for build.xml...
Buildfile:
I've been having trouble getting the optional FTP task to work with
ant-1.4.1 and jdk1.3.1 on W2K, after following all the instructions. But
that's another problem. I tried to diagnose this problem by inserting
this taskdef:
taskdef name=ftp
My bad, I just read the fine print:
Library Dependencies
netcomponents.jar ftp and telnet tasks www.savarese.org/oro/downloads
Frank E. Weiss wrote:
I've been having trouble getting the optional FTP task to work with
ant-1.4.1 and jdk1.3.1 on W2K, after following all the instructions. But
21 matches
Mail list logo
