Enabling Template Files and Velocimacros Resolution

As you probably know, there’s something special about developing applications with template languages (e.g. Velocity and Freemarker): lack of compile-time information prevents from resolving references to included files and library macros. But this is not a problem anymore — IntelliJ IDEA can help you with the use of specially crafted comments.

Let’s have a look at an example module: a.vm file includes b.vm file via velocity.properties file (i. e. relative paths contained in file.resource.loader.path property).

Press Alt+Enter on an unresolved file reference in a.vm and select a module-wide velocity.properties file declaration (looks most appropriate for a single file).

IntelliJ IDEA finds or creates an implicitly included file (any *.vm file that begins with #* @implicitly included *#) and inserts a @velocityproperties comment into it. Then you can select a velocity.properties file from a list of suitable ones found by IntelliJ IDEA.

The comment itself is quite simple:

Base for these relative paths is a folder containing file with comment (in this case, velocity_implicit.vm).

This entry was posted in New Features and tagged , . Bookmark the permalink.

7 Responses to Enabling Template Files and Velocimacros Resolution

  1. I would prefer if those settings could be edited somewhere globally for entire module. Similar way the facets work.

    Moreover if I could, for example, define defaultly imported JSP tag libraries and macros (without explicit definition in templates) as Freemarker itself provides ability to have these defaultly available in all templates. Same way it supports default variables available in page context. This is feature utilized by some frameworks.

  2. Christopher Brown says:

    Support for StringTemplate would be nice, and probably simpler than Velocity and Freemarker to add. It’s by the guy that created ANTLR…

  3. A. Adrian says:

    > I would prefer if those settings could be edited somewhere globally for entire module. Similar way the facets work.
    +1. IMHO this is what facets are for.
    Polluting the template files with such “comments” is not a nice idea (it remembers me of the annotation abuse of some frameworks)

  4. Taras Tielkes says:


    Vote here for StringTemplate support:

  5. Timothy says:

    I am using both @vtlvariable and @vtlmacrolibrary. Is there some way to link a reference to a custom Velocity directive class?

Leave a Reply

Your email address will not be published. Required fields are marked *