Direkt zum Hauptbereich

Simple FMPP Maven Mojo Plugin Documentation

I like to use the FMPP Maven Mojo, but I have not found any documentation about this maven-plugin, I summarize in this blog the basic configuration of this plugin.

About the FMPP Maven Mojo

First a copy-paste description from the site/generate-mojo.html file of the original plugin.

Full name 



Generates artifacts as configured. The output is placed in configured output directory.


  • Requires a Maven 2.0 project to be executed.
  • Binds by default to the lifecycle phase: generate-sources.

Full name


Required Parameters

cfgFileFile1.0Location of the FreeMarker config file.
Default value is: src/main/resources/fmpp/config.fmpp.
outputDirectoryFile-Location of the output files.
Default value is: ${project.build.directory}/generated-sources/fmpp/.
templateDirectoryFile1.0Location of the FreeMarker template files.
Default value is: src/main/resources/fmpp/templates/.

Parameter Details


Location of the FreeMarker config file.
  • Type: java.io.File
  • Since: 1.0
  • Required: Yes
  • Default: src/main/resources/fmpp/config.fmpp


Location of the output files.
  • Type: java.io.File
  • Required: Yes
  • Default: ${project.build.directory}/generated-sources/fmpp/


Location of the FreeMarker template files.
  • Type: java.io.File
  • Since: 1.0
  • Required: Yes
  • Default: src/main/resources/fmpp/templates/


Some examples using the fmpp-maven-plugin

Example 1

Let say you have a fmpp configuration file in src/main/resources/fmpp/config.fmpp. The templates files are located in the directory src/main/resources/fmpp/templates. Finally the generated output files shall go in the target directory under generated-sources/fmpp.

The directory layout for this example:

|- pom.xml
|- src
|  |
|  +- main
|     |
|     +- resources  
|        |
|        + fmpp
|          |
|          +- config.fmpp
|          +- templates
|             |
|             +- ....
|- target
|  |
|  +- generated-sources 
|     |
|     + fmpp
|       |
|       +- ....
The plugin definition

Note: The explicit dependency definition using fmpp version 0.9.15, per default an older version is used missing eg JSON data loader.

Beliebte Posts aus diesem Blog

Using NikSoftware in GIMP

Recently I bought NikSoftware Filters, like Color Efex, or Silver Efex. Usually I use them from Lightroom4, and that’s okay for me.

Now I don’t own Photoshop, but I have installed Gimp 2.8.4, and from time to time I use various Gimp filters like G’MIC, or National Geographic.

But I was not able to use the NikSoftware Filter from Gimp as NikSoftware is shipped as Standalone-Executables, and as Photoshop-Plugins, but not as Gimp-Plugins.

Now there is a Gimp Plugin called PSPI which stands for Photoshop-Plugin.

I gave it try: I installed PSPI and registered the directory of the NikSoftware 32bit plugins. I even was able to invoke the Color Efex Pro 4, and it opened, but the image shown by Color Efex Pro 4 was corrupted.

So I gave up, and forgot about using NikSoftware Filters from Gimp, as I was quite happy using Lightroom and NikSoftware.

But as another user on Google+ asked about using NikSoftware from Gimp, I thought about it again, and then I found a nice Gimp plugin called ShellOut

OnOne Free Lightroom Presets

Auf der Free-Products Webseite von ononesoftware habe ich zwei gratis Lightroom-Presets entdeckt:

onOne Signature Collection Presets for Adobe Lightroom 4 & 5onOne Signature Collection Presets (Vol. 2) for Adobe Lightroom 5 Nach dem Hinterlassen von Vorname, Nachname und Emailadresse habe ich zwei ZIP-Datei gehabt. Das Entpacken und Kopieren der  Verzeichnisse mit den lrtemplate-Dateien unter dem Katalog-Ordner Lightroom-Einstellungen|DevelopPresets und dem Restart von Lightroom selbst, konnte ich die Presets ausprobieren.

Da mir die Vintage-Filter von snapseed so gut gefallen, habe ich gleich die Einstellung Vintage-Grandma's Lemonade ausprobiert:

Die anderen Presets habe ich noch nicht wirklich ausprobiert.
'mal sehen, ob ich noch gefallen an weiteren Preset finde...