"Craig R. McClanahan" wrote:
>
> On Mon, 2 Apr 2001, Waldhoff, Rodney wrote:
>
> > Here's the aforementioned Commons-Collections proposal. The attached JAR
> > has the source, buildfile, etc., as well as the proposal and the initial
> > status.html.
> >
> > To build, you'll need Ant installed and JUnit enabled. You should then be
> > able to run any of clean, build, test, doc and dist.
> >
> > - Rod
> >
>
> 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)?
Not really sure if you had the time to peruse the 75 or so messages on
this subject on sunday... :)
But starting with zero assumptions means that you must include the parts
needed to get the process going (at least ant.jar) and/or grab and build
what you need from CVS.
Or a hybrid where you have a place for people to list, like your
BeanUtils setup.
geir
--
Geir Magnusson Jr. [EMAIL PROTECTED]
Developing for the web? See http://jakarta.apache.org/velocity/
