Dehru Cromer wrote: > I just finished working around the same issue. There was no easy > solution. I couldn't get velocity to stop caching even changing the > velocity properties. One workaround that was suggested on this list > was to reference the css file outside of roller while you're working > on it. I did restarted Tomcat for every velocity change.
Tonight the "Flush cache" button under Preferences -> Mainteance in the roller-ui has worked pretty flawlessly, it indeed flushes the cached css and velocity templates. The thing is that it's a hassle to have to do that from the web ui everytime. I've tried to disable caching in the custom propties file, but it appears to have no impact on the issue. > I've worked with velocity/tomcat before and never had these issues. Yep, I'm pretty confident that this isn't an issue with velocity or tomcat, but with the internal cache system of roller. If I only knew what directory the roller cache system wrote to (or db table if it is a db based caching system) i could easily just delete that one. But I have been unable to figure out even that simple piece of information. > Grind it out! Heh, thanks! A bit of encouraging is always great. cheers -- Fredrik Jonson
