Updating / activating Velocity template changes without Jira restart

[Thomas Maenner]

Hi,

I am playing with some of the velocity templates, namely the releasenote-*.vm.

The only way I have been able to "activate" any changes is by retarting Jira. This makes developement very cumbersome.

Things I've tried include empty browser cache, Jira re-indexing.

Is there any other way achieving this?

Thanks much in advance!

Cheers,

Tom

[Jobin Kuruvilla [Adaptavist] · Accepted solution]

In a development instance, you can play with picking up velocity file changes without a restart.
From <jira-install>/atlassian-jira/WEB-INF/classes/velocity.properties:

1. Change class.resource.loader.cache from true to false
2. Uncomment (remove the # sign from) #velocimacro.library.autoreload=true

[Jared Farrish]

Note as well that you don't have to restart the server for it to understand this change. You can edit the velocity.properties file and JIRA will automatically make the change with no restart.

[Thomas Maenner]

@Jobin Great! That does the trick. Thanks!

@Jared Initiated the restart before the comment came in. Thanks!

[Andreas Gounaris]

Note sure why this is not working for me!

I'm changing the foorer.vm and no way I can view my updates without restarting the server.

velocity.properties file is updated according to the instructions. I verify this in the logs mentioning velocity.properties as a modified file during startup.

It is probably due to #parse() directive mentioned by Jared above.

Any suggestions?

[vijaya reddy]

Hi Jobin,

I am a custom plugin developer on JIRA. We were using JIRA 5.0.X and we modified jirawar/WEB-INF/classes/velocity.properties as mentioned by you and we put our custom plugin vm files under /WEB-INF/classes/ to modify . JIRA was activating vm changes with out restarting JIRA.

But now we started using JIRA 5.2.11 . We need to restart JIRA to take my custom vm file changes into effect. Please suggest.

Regards,

Vijay

[Jason Plumhoff]

I can confirm Jared's comments on the release notes template. The changes listed in the answer had no effect for me.

[Jared Farrish]

See this question for a caveat concerning the #parse() directive, which does not appear to reparse even with the velocity.properties setting Jobin describes below. I have not been able to find a suitable answer other than restarting the server.