[ 
https://issues.apache.org/jira/browse/DRILL-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15609438#comment-15609438
 ] 

ASF GitHub Bot commented on DRILL-4967:
---------------------------------------

GitHub user jinfengni opened a pull request:

    https://github.com/apache/drill/pull/629

    DRILL-4967: Adding template_name to source code generated using freem…

    …arker template.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jinfengni/incubator-drill DRILL-4967

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/drill/pull/629.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #629
    
----
commit 5bd16ba643d5baef8c9a84d2938ca8b497bb5297
Author: Jinfeng Ni <[email protected]>
Date:   2016-09-08T22:50:43Z

    DRILL-4967: Adding template_name to source code generated using freemarker 
template.

----


> Adding template_name to source code generated using freemarker template
> -----------------------------------------------------------------------
>
>                 Key: DRILL-4967
>                 URL: https://issues.apache.org/jira/browse/DRILL-4967
>             Project: Apache Drill
>          Issue Type: Improvement
>    Affects Versions: 1.8.0
>            Reporter: Jinfeng Ni
>            Assignee: Jinfeng Ni
>             Fix For: 1.9.0
>
>
> Drill uses FreeMarker to generate source code in maven build process. It 
> would be helpful if we could put the freemarker template name in the 
> generated source code, so that we could easily locate the template, in case 
> we have to make change to the template.
> Earlier on there was a discussion in the dev list about this idea, and some 
> templates have been doing so. This JIRA is opened to put the template name in 
> all the rest of freemarker templates.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to