> Rod, the build scripts seem to assume that you have JUnit on your > classpath already.
Essentially, that's correct. Actually I was assuming that you had Ant "fully JUnit enabled"--i.e., the junit task registered by default, the junit.jar in your ANT_HOME/lib. That's what I meant by "you'll need Ant installed and JUnit enabled" in my original email, but I suppose that wasn't clear.
> Do you think we could make an Ant property for locating
> JUnit, and add it to the constructed classpath explicitly
> (I used "junit.home" in beanutils for this)?
Sure. To be consistent with the other external dependencies in the other two proposals, I just added a junit.jar property to the build.properties.sample. I don't mind the junit.home approach much either, but I thought I'd let that debate die down first.
I also switched to using <java> to during test rather than <junit>, so the junit task itself isn't needed either.
I did this to all three of my proposals in the sandbox (collections/pool/dbcp). Hopefully it should build a little more cleanly now.
- Rod
