https://github.com/wouterd/mustache-maven-plugin

A maven plugin to process mustache templates in a maven build
https://github.com/wouterd/mustache-maven-plugin

Last synced: 12 months ago
JSON representation

A maven plugin to process mustache templates in a maven build

• Host: GitHub
• URL: https://github.com/wouterd/mustache-maven-plugin
• Owner: wouterd
• License: apache-2.0
• Created: 2014-02-04T09:52:27.000Z (over 12 years ago)
• Default Branch: master
• Last Pushed: 2020-09-29T15:41:04.000Z (almost 6 years ago)
• Last Synced: 2025-07-18T02:50:30.828Z (12 months ago)
• Language: Java
• Homepage:
• Size: 32.2 KB
• Stars: 4
• Watchers: 1
• Forks: 1
• Open Issues: 2
• Metadata Files:
  • Readme: README.md
  • Changelog: CHANGELOG.md
  • License: LICENSE

Awesome Lists containing this project

README

          
mustache-maven-plugin

=====================

[![Build Status](https://travis-ci.org/wouterd/mustache-maven-plugin.png?branch=master)](https://travis-ci.org/wouterd/mustache-maven-plugin)

A maven plugin to process mustache templates in a maven build

# Description

This maven plugin allows you to define one or more contexts in YAML and push those through one or more mustache templates 

during your maven build. I've been using this to make my application configuration files (context.xml f.ex) generic and 

generate these during the deploys to various environments. (Using ruby-mustache)

# About this document

As the documentation evolves with different plugin versions, be sure that before you read on that:

- You check that you are watching the right tag

- Switch to the right tag to read the right documentation.

The README of the master branch will cover the current development version and not cover the current released version.

# Usage

Include the following code snippet in your pom as a plugin:

The <configuration> element is the most interesting, here you can specify a global context and a sequence of 

templates. These templates are executed in order of appearance. If you want, you can use files generated in a next step. 

Each template has three fields: templateFile, outputPath and context. Context is optional and specifies a YAML formated 

context. templateFile points to the mustache template to render. outputPath tells the plugin where to write the 

generated output. The context element can either contain valid YAML, starting with a line containing just:

    ---

    

Or it can contain file:[filename], where filename points to a file with valid YAML markup.

The `` element specifies the encoding for the input and output files. This defaults to 

`project.build.sourceEncoding` set in Maven.

                    

    

        net.wouterdanes

        mustache-maven-plugin

        1.1

        

            

                run-mustache-template

                validate

                

                    mustache

                

            

        

        

            UTF-8

            file:${project.basedir}/local/server-configuration.yml

            

                

                    ${project.basedir}/common/src/main/conf/context.xml.mustache

                    ${generated.context.xml.location}

                

                

                    ${project.basedir}/common/src/main/conf/hst-config-environment-specific.properties.mustache

                    ${generated.hst.properties.env.specific.location}

                

            

        

    

## Property Interpolation

You can include maven properties into your context by using the maven property syntax like this: `${propertyName}`.

All project properties can be referenced.