At 06:14 3/4/01 -0700, Craig R. McClanahan wrote:
>Rod, the build scripts seem to assume that you have JUnit on your
>classpath already. I think we should start with zero assumptions about
>the contents of the user's classpath (even to the point of ignoring it) in
>order to minimize unintended dependencies on build environment
>assumptions. 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)?
How about junit.jar then it doesn't matter what it is named (ie junit.jar
vs junit-3.2.jar ). This is the pattern I use to name dependencies in avalon.
Cheers,
Pete
*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof." |
| - John Kenneth Galbraith |
*-----------------------------------------------------*
