available file=${build.test.classes}/cactus.fileset
property=cactus.tests.exist/
Here's what I'd rather do (as an example):
available property=cactus.tests.exist
filePattern=**/cactus/**/
I've gone through the manual and nothing jumped out at me.
PC
Paul Christmann
pathelement location=bar/
/path
/properties
PC
Paul Christmann
Prior Artisans
504-587-9072
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Yep. That patch is included in the modifications I submitted as an
attachment to bug 11321
(http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11321).
PC
-Original Message-
From: Nicola Ken Barozzi [mailto:nicolaken;apache.org]
Sent: Thursday, October 24, 2002 9:55 AM
To: Ant Users
, allowing me to invoke my build file from anywhere in my
heirarchy; is there another way to get this behavior without ANT_ARGS?
PC
Paul Christmann
Prior Artisans
504-587-9072
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
had a dependency on init anyway. However, the value we're
getting from full sharing of properties across our builds more than
offsets this.
Paul C.
Paul Christmann
Prior Artisans
504-587-9072
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL
? Is
there a way of doing comparable things with existing tools?
PC
Paul Christmann
Prior Artisans
504-587-9072
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
that functionality consolidated in a target invoked once
via dependency and other times via antcall. The problem came from the
loadfile property.)
PC
Paul Christmann
Prior Artisans
504-587-9072
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL
on 1.4.0 until the next 1.4.1 release comes out.
Paul Christmann
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
an issue with the stylesheet (and I'm still learning
XSL syntax to see if I can clean that up)
THanks for any thoughts,
Paul Christmann
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
FYI -
I downloaded the binary version of 1.5 b3 this morning, and my JUnit
tests worked fine (I was receiving a VerifyError when using 1.5 b2
binary).
Not sure if anything explicit was done to address this, but I'll assume
you waved your magic fingers over the keyboard! Thanks!
Paul C.
I just upgraded from 1.5alpha (built from CVS in mid-April) to the 1.5b2
release (downloaded the binary distribution).
When I did this, my unit test target stopped working -- all unit tests
reported the following exception:
[junit] java.lang.VerifyError: (class:
-Original Message-
From: Magesh Umasankar [mailto:[EMAIL PROTECTED]]
Which JDK are you using and on which OS?
Windows 2000, JDK 1.4 compiler
Surprising nobody else has reported this so far!
My thoughts as well; the only things I could think of are:
a) I screwed up the
12 matches
Mail list logo
