Liferay 6.2 Theme with JRebelLiferay 6.2 Theme with JRebelhttps://liferay.dev/en/c/message_boards/find_thread?p_l_id=119785333&threadId=315301642024-03-28T23:51:23Z2024-03-28T23:51:23ZRE: Liferay 6.2 Theme with JRebelDmitry Sergeevhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=323106162013-12-10T20:31:32Z2013-12-10T20:31:32ZThank you so much! I had spent 3 evenings trying to get theme working with jrebel untill it appeared to me that first time it updates successfully.Dmitry Sergeev2013-12-10T20:31:32ZRE: Liferay 6.2 Theme with JRebelAndres Luukhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=315336122013-11-15T08:16:52Z2013-11-15T08:16:52ZThis seems like a reasonable suggestion for a JRebel user.<br /><br />On JRebels side we don't disable Liferay caches, we relay on the Liferay development mode todo it.Andres Luuk2013-11-15T08:16:52ZLiferay 6.2 Theme with JRebelMuhammed Shakirhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=315301632013-11-15T06:15:00Z2013-11-15T06:15:00ZUntil 6.1.x the property which decided that the velocity templates will be reloaded each time the page is visited was – velocity.engine.resource.manager.cache.enabled=false . From Liferay 6.2 onwards this property has changed to : velocity.engine.resource.modification.check.interval=0 (0 means each time it will reload the template, -1 would mean cache it ones and keep it indefinitely and > 1 for .e.g. 60 would mean, cache the template for 60 milliseconds). In development mode, keeping velocity.engine.resource.modification.check.interval=0<br />is extremely important for themes to reflect changes you do in .vm files and see the effect of your change without redeploying the theme. By the way, I am using JRebel and it did not work with themes because of the above property.<br /><br />Once I made