On Mon, 18 Mar 2002 00:17, Leif Mortenson wrote:
> What about adding an init task to the builds which checks for the pressence
> of all required jars.  If any are missing then the build will fail with a
> message telling them to run 'ant update-ant-jars'.  This task would
> automatically download and install all of the required jars from our server
> and install them into the correct ant directories.  The user then reruns
> and and everything will work.  Is there a way to have ant check the dates
> of the required files?  It would  be nice if the build could tell users to
> rerun the update whenever any of the required jar versions are changed as
> well.

I would seriously think about strangling anyone who tried to update my ant 
installation in the build process. I don't think this is the solution. 
Hopefully the BUILDING.txt instructions should help a little though.

> Thoughts?  This was actually Ryan's idea?  (You had asked him if he was a
> committer the other day.  I would be +1 :-)

So would I ;)

> > junitperf.jar shouldn't be needed ... but the rest of them are.
> > junitperf.jar could probably be added in wherever it is needed. It is an
> > unfortunate "feature" of ant that these need to be in the same
> > classloader as the rest of the task.
>
> There are a few tests in the all subproject that use it.

True but it sjhould not need to go int ant/lib - it should just bereferenced 
from whatever project needs it via properties.

-- 
Cheers,

Pete

------------------------------
Kitsch never goes out of style
------------------------------

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to