# HG changeset patch # User Dirk Olmes # Date 1623993880 -7200 # Node ID be0331916375c2a439a49518fa1f180cb120b306 # Parent ee048ed76ea12d27d37ef08557f1703cdd61374a# Parent 6b2c946700562fce7f871d178fab3a95307953d2 README diff -r 6b2c94670056 -r be0331916375 content/Maven/gmaven-string-template-engine.md --- a/content/Maven/gmaven-string-template-engine.md Thu Jun 17 17:07:24 2021 +0200 +++ b/content/Maven/gmaven-string-template-engine.md Fri Jun 18 07:24:40 2021 +0200 @@ -1,10 +1,10 @@ Title: Quick templating with gmaven and GStringTemplateEngine -Date: 2020-06-16 +Date: 2021-06-16 Lang: en At work I have come across the requirement to generate some files based on the info in a `pom.xml`. Maven's [resource filtering](https://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html) feature would be the first thing that comes to mind but unfortunately it's not powerful enough for my use case. I had to generate a file based on the dependencies that are referenced in the project. -A bit of googling found all kinds of outdated or unsupported maven plugins but nothing that would fit my use case directly. Finally I gave up and started to hack something together in groovy. +A bit of googling found all kinds of outdated or unsupported maven plugins but nothing that would fit my use case directly. Finally I gave up and started to hack something together in groovy. As it turns out groovy comes with a templating engine built in: `groovy.text.GStringTemplateEngine`. Using it is fairly straightforward from Maven: