>>I am a little worried about this making it more difficult for new users to >>checkout excalibur and start using it though. >> > > Me too. I once proposed the following to the rest of ant-dev but no one was > interested. Basically I create a binary distribution of ant and commonly used > libraries so that users just need to download the "Ant Developers Toolkit" > and start using it straight away and don't have to worry about all the icky > classpath stuff. > > Basically it would consist of the latest ant that contains "preinstalled" > versions of latest > * xalan > * ant > * junit > * xerces (or crimson) > * jdepend > * ... > > No one -1'ed it over in ant land so I can still do this. Would this be enough > do you think? If not can you think of something else that doesn't require > putting ant in CVS ;)
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. Thoughts? This was actually Ryan's idea? (You had asked him if he was a committer the other day. I would be +1 :-) >>I needed to do the following: >>Download and install Ant. >>Download and install the optional jar. >>And download and add the following jars to the ant/lib directory: >>junit.jar, junitperf.jar, xalan-2.2.0-D13.jar, xml-apis.jar >> > > 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. >>Anyway, I backed out all the work I did today to get things working with >>the framework ant. (sigh) >> > > sorry about that. No problem, I should have stopped and thought... "Why would Peter have committed all of these changes when they didn't work. Could it be that I am doing something wrong??? Naw....". (sigh) Cheers, Leif -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
