[
https://issues.apache.org/jira/browse/AVRO-963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158741#comment-13158741
]
George Fletcher commented on AVRO-963:
--------------------------------------
It's pretty straight forward to leverage the SpecificCompiler.java
setTemplateDir() method via a configuration parameter. However, this still
requires the templates to be part of the java class path. Is that acceptable?
For example in the *Mojo.java files...
{code}
/**
*
* Override the default location for the velocity templates
* @parameter
*/
private String templateDir = null;
@Override
protected void doCompile (...) {
...
SpecificCompiler compiler = new SpecificCompiler(protocol);
if (this.templateDir != null) {
compiler.setTemplateDir(this.templateDir);
}
compiler.setStringType(StringType.valueOf(stringType));
compiler.compileToDestination(src, outputDirectory);
...
}
{code}
> Allow
> ------
>
> Key: AVRO-963
> URL: https://issues.apache.org/jira/browse/AVRO-963
> Project: Avro
> Issue Type: Improvement
> Components: java
> Affects Versions: 1.6.1
> Reporter: George Fletcher
> Priority: Minor
>
> It is currently not possible to override the location of the velocity
> templates except via overriding a system property which requires a maven
> command line option. Allow for the location of the templates to be specified
> via a configuration parameter in the avro maven plugin.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
