Story: plugin developers want to create plugins with lots of features. Most plugins use Velocity templates for their UI features.

Problem: Velocity files in JIRA can use #parse and #macro to make them scale better. Plugins can't use #parse at all, and #macro only works within the same .vm file.
This makes it hard for plugins to scale. Developing and debugging a large, monolithic .vm file is hard to get right.

Idea: modify the DefaultVelocityManager so that when it is used by a plugin it changes the Velocity engine properties and adds the resources directory as a valid TEMPLATE_ROOT for finding macros and .vm files to include. Document this with a small reference plugin that shows how to use these Velocity features to improve your own plugin.