OK, after a couple of weeks of chaos with Tomcat, it looks like we're finally getting it under control. The daily build has gone without a hitch for the past few days in a row, which is positive evidence.
I am currently thinking of making the stable release early next week, barring any problems that come up this week. If Aaron, Cedric, and Hongbing (at least) could provide some feedback about the stability of their local installations under the new regime, that would be great. The status, as I understand it, is: (a) Use Tomcat 5.5.20. For stability purposes, if you've been having problems, you might want to unpack a new one to test out this latest round of changes. (b) Update your SVN repository. This will result in some changes to the build procedure. The context.xml file is no longer generated on the fly, but is instead in the build/war/META-INF directory. There is no appbase specified. The result is that hackystat is copied into the webapps directory. This is not a big new overhead as it might seem, since previously (due to jar locking issues) Tomcat was making copies of Hackystat in the temp directory anyway. We're now updated to more recent versions of jstl and so forth (thanks Cedric!). I checked with Hongbing yesterday and he's been developing without problems under this new scheme for the past few days. I have been under water and working on an NSF proposal for Hackystat, so I haven't had a chance, but the proposal is submitted so I will definitely do some hacking later this week. So, good luck, happy hacking, let me know how it goes. I'm keeping my fingers crossed. Cheers, Philip
