Can you bring that down to just one 1.5 jar in the system? We changed some classloading stuff in 1.5 to deal with some other common classloading problems. I'm wondering if you needed 3 jars before but now that is causing this problem. Just a guess...
On 3/23/07, Michael Giroux <[EMAIL PROTECTED]> wrote:
On 3/23/07, Will Glass-Husain <[EMAIL PROTECTED]> wrote: > Another point of speculation -- could there be multiple instances of > the Velocity jar in your Eclipse distrib? It might be trying to pull > these classes from a different velocity.jar. > > WILL There are three copies of the 1.5 jar in the system, but there were 3 copies of the 1.4 jar and everything was running fine with that config, so I'm surprised there would be an issue. I must have touched something else and just am not aware of it. Thanks for all the pointers, but I think I've got a class loader issue that I'll have to sort out in Eclipse. Michael --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
