Subject: Grouper Developers Forum
- From: "Tom Zeller" <>
- To: "Grouper Dev" <>
- Subject: running tests ?
- Date: Mon, 19 Jan 2009 13:13:07 -0600
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:mime-version:content-type :x-google-sender-auth; b=EQ/J066WF92/qIoCbD4R5qfqNQauTg9cKj2nmmYNrwZNR0meuWoj4wLSB64dWa337c D7xsFvK0nQFtp34mtK61znzEOBWSHsqPgvDkYNYRad3rJMQDjQI8qR7V1i6zFMmNbch5 k8iRusbm+z2Jfufd5j/d9Uci458VcY9iNG92Y=
I suggest we (1) run tests from ant (not gsh) and (2) don't include jars solely necessary for testing in the binary grouper+ldappc distribution.
There are ~20 apacheds jars required for ldappc junit tests. It seems annoying to include those jars in a binary grouper distribution, since most folks won't need them, and most folks using a binary distribution are unlikely to run junit tests.
I also suggest using ant instead of gsh for testing, since the classpath can be arranged flexibly. Otherwise, I'm not sure how too prefix the classpath with confForTest/ when running bin/gsh.sh -test, which needs to find ldappc.xml.
- running tests ?, Tom Zeller, 01/19/2009
Archive powered by MHonArc 2.6.16.