>This could be your issue: http://stackoverflow.com/a/8656527/696632
It picks up the changes to the contents of the template macros ok, so its unlikely to be the tomcat cache. It won't pick up the new macros. I though it might be a list/array that stores the names that needs to be cleared/reset when the macro is reloaded, but it looked much more complicated. Cheers Greg On 4 January 2017 at 17:34, Michael Osipov <micha...@apache.org> wrote: > Am 2017-01-04 um 14:43 schrieb Greg Huber: > >> The was one issue that has been around for ages, and I am not sure if it >> is >> possible to fix it. >> >> If I have added a new macro into a velocity template file loaded via a >> resource loader, I have to shut down the container (tomcat) and restart >> for >> it to be picked up. I will allow the contents of the macro to be changed >> but not a new macro. I did try to see if I could fix it but without much >> success. >> >> my velocity.properties : >> .. >> webapp.resource.loader.description=Webapp Resource Loader >> webapp.resource.loader.class=rendering.velocity.WebappResourceLoader >> webapp.resource.loader.cache=true >> webapp.resource.loader.path=/WEB-INF/velocity,/WEB-INF/veloc >> ity/templates,/WEB-INF/velocity/templates/feeds,/WEB-INF/ >> velocity/templates/emails >> ... >> >> If you are now familiar with the code you might be in a better position to >> see why I have to shut down for it to be picked up. >> > > This could be your issue: http://stackoverflow.com/a/8656527/696632 > > Michael > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org > For additional commands, e-mail: dev-h...@velocity.apache.org > >