I think a good start would be to file a JIRA ticket on the templating mojo:
http://mojo.codehaus.org/templating-maven-plugin/issue-tracking.html
Specify the templating component.
/Anders
On Wed, May 29, 2013 at 12:02 PM, Wouter <wowt...@gmail.com> wrote:
> Thanks for your answers. Admittedly, I didn't find the templating
> plugin, perhaps because the project info plugin predates it and I just
> did a quick check before sending this message.
>
> I like Stephen's solution. It seems that what this extension would do is a
> super set of what the project info plugin does, so it's just more generic
> and
> I don't see major drawbacks.
>
> As for my involvement, I suppose it could end here, but I'd be happy
> to contribute where I can, provided I have time to donate.
>
>
> On Tue, May 28, 2013 at 12:05 PM, Stephen Connolly
> <stephen.alan.conno...@gmail.com> wrote:
> > Well I had a different idea...
> >
> > The plan is to add support for templating engines to the
> > templating-maven-plugin.
> >
> > As such I would expect additional goals (2 of them) for templating, e.g.
> >
> > generate-[test-]sources mojos
> >
> > They would presumably take a configuration that identified the templating
> > engine, e.g.
> >
> > <configuration>
> > <templates>
> > <template>
> > <source>src/templates/foo.java.hbs<source>
> > <engine>handlebars</engine>
> > <properties>
> > <package>com.mypackage.foo</package>
> > <title>blah blah</title>
> > </properties>
> > </template>
> > </templates>
> > </configuration>
> >
> > Now as such, it would make sense when resolving the template, to not only
> > pick up from the project but if that fails, fall back to the plugin's
> > classpath (just as pmd:pmd and checkstyle:checkstyle do for their
> rulesets)
> >
> > In such a case, this project info plugin would actually be either an
> engine
> > that does not need a source, or a standard template using the default
> > engine, iterating all properties and skipping a property called
> "package" to
> > use that for the package name instead.
> >
> > e.g. in handlebars you would probably have
> >
> > package {{properties.package}};
> >
> > public final class ProjectInfo {
> > private ProjectInfo() {
> > }
> >
> > private static final class ResourceHolder {
> > private static final ProjectInfo INSTANCE = new ProjectInfo();
> > }
> >
> > public static ProjectInfo instance() {
> > return ResourceHolder.INSTANCE;
> > }
> >
> > {{#each propertyEntries}}
> > public String get{{key}}() {
> > return "{{value}}";
> > }
> > {{/each}}
> > }
> >
> > (yeah I know you'd probably want to use velocity for this one so you can
> > handle escaping of special characters in the {{key}} and the {{value}}
> but
> > you get the idea)
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>
